Forum Discussion
13 Replies
- Robert5203Ideator I
If you want to conditionally stop a Flow but under normal circumstances so it doesn't appear as an error, use Continue If as long as all lists are set to the same item type. Combine a list of objects with key and value properties into a single JSON object.
- AmbujIdeator I
Hi Robert
Can you please give sample code to work on the lines of what you have explained above?
Thanks
Ambuj
- PrathyushaIdeator I
Hi Ambuj,
Did you figure out the process of associating two or more workflows to the same Item type?
Thanks,
Prathyusha
- AmbujIdeator I
Hi Pratyusha
Check the solution given by Gopikrishnan on the same thread.
Ambuj
- Former Member
Thanks For Sharing. I Will also share with my friends.
- JayrajvhIdeator I
What is the reason to allow end user to choose a workflow? I can describe normal scenario and possible ways to achieve this.
- Normally default workflow is initiated automatically when a new Item is created.
- You can avoid it by not specifying default workflow but rather specifying a workflow on a particular lifecycle state. In such case Workflow will be initiated when Item reaches that particular LC state.
- Now above ability can be utilized to initiate different workflows. You can configure different classifications on Item and specify LC for each classification. On first LC state of these LC maps you can attach Classification specific Workflows.
At the outset, just using configurations, you can initiate default workflow or Classification Specific Workflow configured on Classification specific LC. I am not aware if there can be a way to allow end user to choose a workflow.
- GopikrishnanIdeator I
Hi
Yes, it is possible to allow user to select the workflow using some action. Refer this blog
https://arastutorials.blogspot.com/2021/01/dynamicWorkflowInitate.html
- JayrajvhIdeator I
Interesting solution Gopikrishnan . This gives flexibility to end user about selection of Workflow. Its really the customer's choice to standardize the process and still allow possible flexibility.
- YoroflowIdeator I
Thanks for this information
- canzopIdeator I
Each workitem type should be driven by only one workflow.
To solve a scenario like that, I´ve create a more complex workflow where a certain state flows for two possible states through of different actions, in your case doc changes or code changes. And back to the final state after the specific job has been done to solve doc or code needs.....