Open henrikStr opened 2 years ago
Hello Henrik,
sorry for my late reply. First question before debugging what's going on : -) LDA and ODA are defined in the Actor column? Here is an example that works:
[cid:19a7944e-bef6-488f-820c-ac02baa6579b]
Serge Luca
Business Applications (Power Automate & PowerApps) MVP
Creator of the open-source Power Platform BPM Toolkit
https://github.com/sergeluca/Power-Platform-BPM-Toolkit
Power Platform Associates, Belgium
P: +32 472 885 928
E: @.**@.>
Bloghttp://sergeluca.wordpress.com/ | Linkedin http://www.linkedin.com/in/sergeluca | Twitter http://www.twitter.com/sergeluca | Webhttp://www.shareql.com/
[cid:92dc50b2-f5ca-4621-9977-ad50ba719e8d]
[cid:9622d416-5d4e-4a54-917a-4fb54e10bfb9]
From: henrikStr @.> Sent: Tuesday, 26 July 2022 11:53 To: sergeluca/Power-Platform-BPM-Toolkit @.> Cc: Subscribed @.***> Subject: [sergeluca/Power-Platform-BPM-Toolkit] Goto Step (Issue #13)
Hi,
I am trying to test out the new 2022 version with some meta workflow definitions we might like to use later on. I have some steps that should skip a few steps if the Approval is positive. I thought Goto Step in the Meta Workflow definition would be the parameter I could use for that, so I entered the Step Number to which I would the the workflow instance to skip to. But it seems like Goto Step hat no impact on the workflow. The workflow instance will just go to the next step available.
Is there a way to accomplish my goal? [BPMToolkit error]https://user-images.githubusercontent.com/85345351/180978134-2b1d79da-873c-42cc-8154-f3ddd0976458.PNG
— Reply to this email directly, view it on GitHubhttps://github.com/sergeluca/Power-Platform-BPM-Toolkit/issues/13, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXEHPYXBTAIB7PCODUNPPDVV6YRBANCNFSM54VJLGRA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi Serge,
Yes LDA and ODA are defined as actors. Jumping to a specific actor after the status of a step is negative works, just as defined in the meta definition.
My problem is that I want the workflow to skip the LDA and ODA steps and go directly to step 7 if step no.2 gives a positive feedback. Thats what I thought Goto Step would be used for. To give a step a following step.
Henrik, can you show the column names in your screenshot?
Serge Luca
Business Applications (Power Automate & PowerApps) MVP
Creator of the open-source Power Platform BPM Toolkit
https://github.com/sergeluca/Power-Platform-BPM-Toolkit
Power Platform Associates, Belgium
P: +32 472 885 928
E: @.**@.>
Bloghttp://sergeluca.wordpress.com/ | Linkedin http://www.linkedin.com/in/sergeluca | Twitter http://www.twitter.com/sergeluca | Webhttp://www.shareql.com/
[cid:fe04f35d-98d3-4b58-9a87-88d1b119b4c5]
[cid:57c9c6c7-d629-42d8-bb92-2c813b80bf2d]
From: henrikStr @.> Sent: Tuesday, 26 July 2022 11:53 To: sergeluca/Power-Platform-BPM-Toolkit @.> Cc: Subscribed @.***> Subject: [sergeluca/Power-Platform-BPM-Toolkit] Goto Step (Issue #13)
Hi,
I am trying to test out the new 2022 version with some meta workflow definitions we might like to use later on. I have some steps that should skip a few steps if the Approval is positive. I thought Goto Step in the Meta Workflow definition would be the parameter I could use for that, so I entered the Step Number to which I would the the workflow instance to skip to. But it seems like Goto Step hat no impact on the workflow. The workflow instance will just go to the next step available.
Is there a way to accomplish my goal? [BPMToolkit error]https://user-images.githubusercontent.com/85345351/180978134-2b1d79da-873c-42cc-8154-f3ddd0976458.PNG
— Reply to this email directly, view it on GitHubhttps://github.com/sergeluca/Power-Platform-BPM-Toolkit/issues/13, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXEHPYXBTAIB7PCODUNPPDVV6YRBANCNFSM54VJLGRA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Ah sorry. Here you are
the Goto step column is not used yet in this version. Only If Goto is used by the current version of the BPM Toolkit. The reason why I haven't implemented that yet is that the step number might change during the workflow execution if someone dynamically adds a step in the workflow from the UI I should have removed to Goto step from the setup script to make it less confusing. But I understand your concern because you want to go to step 7 (behorde) which is used in different steps so that the goto behorde won't work here, right ? -->workaround: can't you define a specific actor, like behorde2 have a goto behorde2 ?
Serge Luca
Office Applications and Services (Office 365) MVP
Business Applications (Power Automate & PowerApps) MVP
Creator of the open-source Power Platform BPM Toolkit
https://github.com/sergeluca/Power-Platform-BPM-Toolkit
Power Platform Associates, Belgium
P: +32 472 885 928
E: @.**@.>
Bloghttp://sergeluca.wordpress.com/ | Linkedin http://www.linkedin.com/in/sergeluca | Twitter http://www.twitter.com/sergeluca | Webhttp://www.shareql.com/
[cid:116d3197-dee3-4dc3-999f-7da486c5d252]
[cid:f6f31018-0bc5-470e-bb32-b70dd0a37ec9]
From: henrikStr @.> Sent: Wednesday, 27 July 2022 13:24 To: sergeluca/Power-Platform-BPM-Toolkit @.> Cc: serge Luca @.>; Comment @.> Subject: Re: [sergeluca/Power-Platform-BPM-Toolkit] Goto Step (Issue #13)
Ah sorry. Here you are
[BPMToolkit2]https://user-images.githubusercontent.com/85345351/181235372-d053e295-3fde-447e-b971-f99fea6b6a47.PNG
— Reply to this email directly, view it on GitHubhttps://github.com/sergeluca/Power-Platform-BPM-Toolkit/issues/13#issuecomment-1196603072, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXEHP7RN46S2RJA46ZLQELVWEL65ANCNFSM54VJLGRA. You are receiving this because you commented.Message ID: @.***>
Hi,
I am trying to test out the new 2022 version with some meta workflow definitions we might like to use later on. I have some steps that should skip a few steps if the Approval is positive. I thought Goto Step in the Meta Workflow definition would be the parameter I could use for that, so I entered the Step Number to which I would the the workflow instance to skip to. But it seems like Goto Step hat no impact on the workflow. The workflow instance will just go to the next step available.
Is there a way to accomplish my goal?