Skip to main content
Nintex Community Menu Bar

Creating Multiple Tasks in a workflow

  • May 4, 2022
  • 8 replies
  • 65 views
  • Translate
S

Hi Team. I have a problem I am finding it hard to come up with a solution for creating a workflow  in k2 with following steps

1.   Client sends a ticket to a developer requesting help.

2.  Developer receives that ticket with info: Solve, Cant solve,Need more information about the problem.

3.Developer needs to take action and send a feedback to a sender if he/she can solve,not solve or needs information .

if he/she cant solve,he/she needs to send to someone else who can solve(Project manager)

project will solve and send back to Client.

 

if Developer solve he will send to a client, if he needs more information he will send back to client...Client will give more details until issue is solved.

 

How can I solve this??

 

Thank You in advanced

 

    Did this topic help you find an answer to your question?

    T
    Forum|alt.badge.img+13
    Can you let us know which part of this you are having difficulty with? It seems like you've laid it all out quite logically
    Translate
    S
    • SA4
    • May 5, 2022

    I Created a workflow and is working but when I receive email notifications about the details of call, references I have used they don't appear. Its empty while on I did insert references.

    Maybe this screenshots will help you understand my problem. Wonder where did I go wrong.

    Translate
    2 Attachments
    S
    • SA4
    • May 9, 2022

    I haven't receive any solution at the moment, anyone who sis willing to help may please intervene coz I don't know where did I go wrong.

    Translate
    W

    Are you sure that your data source has data populated in those fields?

     

    Does that task event fall inside of a loop? If so, you will need to drag the required fields from the reference item section that was generated from the loop creation step.

     

    As a last resort, you can always do a Smart Object read method before the task, assign the return properties to variables, and then use those variables in the email.

     

    Translate
    T
    Forum|alt.badge.img+13
    What is odd is that even the Date isn't coming over, which is not a data field but an environment field. Can you confirm that you've deployed the latest version of this workflow and tested with a new instance of the process (to make sure it is actually using the latest deployed version)?
    Translate
    S
    • SA4
    • May 11, 2022

    I did and received the same issue

    Translate
    S
    • SA4
    • May 11, 2022

    I did and still receiving the same problem

    Translate
    T
    Forum|alt.badge.img+13
    Very strange! Can you confirm that if you change some static text in the body of your email that the change comes across in a new test? I'm focusing on that Date not coming into the email as "Now" should always have a value.
    Translate

    Reply


    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsCookie Settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie Settings