As a part of the product development, We have to implement a workflow engine. Currently the workflow is simple one i.e , there could be multiple states for ex: 1,2,3,4,5. The user can select a combination of states for ex
Work flow 1: 1->2->3->4->5
Work flow 2: 1->4->5
Work flow 3: 5
The plan is to implement the states in the workflow using Lambdas, ECS Tasks, App Runner etc and the orchestration using Step Functions . Since the workflows are created by users , we are looking for a way to translate the user selection in to a step function state machine. We are discussing various approaches
Create a step function programmatically based on the user selection
Create a catch all work flow with a Choice , which would a state based on it is selected in the workflow
Implement a decider function based approach
We found some references in the following post: AWS Step Functions with dynamic steps
Any other recommendation would be really appreciated. Thanks in advance
Related
I'm working on a Rasa (Open Source) project, I need to represent the diagram flow in a chatbot.
The main problem is following the conditional flow as the user can say yes or no and modify the flow of the conversation.
I would like to know how I could build a chatbot that contemplates all the possibilities represented in the diagram and the others that are outside it, using Rasa.
In other words, a chatbot that responds to the user according to his previous response.
Please.
flowchart
A "solution" I found was to create a story for each possible path, but it is "unfeasible" due to the number of stories. (there are 9 other diagrams like this one).
Regarding the flow and how you can map your designed diagrams into Rasa, you try to use one universal story/rule to make your structure more modular. You can find parts of the flow in your diagram that are being repeated on the other ones also and create your story/rule(s) out of them to be used in different flows. Rasa also supports checkpoint, which let you manage your stories in a more restrictive way.
For getting users' responses and acting accordingly, you need to deploy Rasa forms and action in your story/rule(s) for extracting those 'entities` you want to get from users and manipulate them.
I'm new to microsoft planner 365 and I think it's a great tool.
I do not want users to access my plan (board). Is there any way I can create an online form that can be shared to other users to allow them to submit requests and it adds tasks directly to a bucket category?
(Except using Power Automate?
using forms and Power Automate this can be setup in less than 5 minutes using the below template that is provided.
if you have reasons for not taking the simple approach, then of course you can build the same using a mirad of other tools and technologies.
As a final step then create the Task Using the Graph API
Is it possible to customize a work item programmatically (through code) instead of using the UI (Process)? I want to add a button to create two specific work items, provided some conditions are fulfilled.
I tried to achieve the above requirement using UI. However, it doesn't seem to be possible.
For processes using the Inheritance model. API’s for everything you need to create and manage a process through code. This includes work item types, pages, groups, fields, states, rules, etc. Check Work Item Tracking Process APIs at the following site:
https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-5.0
For Hosted XML processes. API’s for checking to see if the process exists, importing, and exporting a Hosted XML process. Check Work Item Tracking Process Template APIs.
More details, you could refer to the following blog:
https://devblogs.microsoft.com/devops/announcing-new-rest-apis-for-process-customization/
I want to generate simple document approval system in workflow foundation. We have already available document approval process example on MSDN but it is quite complex to understand as it involves WCf and all. I just want a startup with workflow foundation so it's better if I follow step by step guide tutorial. Thanks in advance.
I wrote a blog post on how to implement a simple approval workflow using emails and ASP.Net MVC.
http://blog.petegoo.com/index.php/2010/08/22/workflow-4-email-approval-sample/
I think http://visualstudiogallery.msdn.microsoft.com/7fe6f504-a58d-456e-8f55-e64bddc81a41 is a good tutorial to start with. It is better if you try this with state machine type of workflow because you need several user inputs from outside the workflow in several stages.
I want to track my custom activities' property values in my own tracking service, .i.e. I don't need it in the built in SQL tracking service. I have been successful in reproducing the SQL tracking service in that I can see the worklfow and activity states etc. but I want to see property values also.
We are writing many workflows for a document management system (DMS) using its own workflow engine that is based on MS WF. I can therefore not change the workflow runtime (if it was needed). The solution has to work with the embedded functionality of the underlying Microsoft workflow runtime.
Our workflows typically do database lookups through custom activities we write. These lookup values are then passed on to other activities for program flow or for persistence into the DMS. It would be great if we can see what these lookup values are at runtime and in fact the values of the DMS own activities' properties.
From my (admittedly limited) knowledge of MS's Workflow, the correct approach is to publish updates to your tracking service from within the workflow -- ie, if your workflow does some step, it should go to the tracking service and say "I did X". Your tracking service can record this information to answer any subsequent queries about what the workflow did (and what the various property values were at the time).
The essential point is that the WF engine is useful for running workflows - but is not very good at reporting on the progress of those workflows.
If you do have some control over the WF engine (you say its "based on MS WF") then one option may be to make your WF Engine publish such updates for all workflows. That may allow you to forgo explicit updates within your actual workflow definitions. However, if you really can't make any changes to the engine, then this won't work.