iam facing issue in jbpm as iam new to the jbpm.
i need to re-start the process or need to jump back to the previous process.
can you any one please suggest how to do it
my flow is
before saving, based on condition , i need to repocess the flow from getDeclaration.
can any one guide me to do this.
please let me know, if any extra information needed
Here is an example of how you can return to a previous task.
Related
I'm sure this is a dumb question, but I'm wondering if somebody could please inform me of best practice here. I'm using patroni and pgbackrest for cluster management and backup, and in the case of somebody screwing something up I want them to be able to restore to a point in time. Then, if they don't like that restoration, to be able to re-restore to another point in time, e.g. 5 minutes in the future or the past.
The problem is, the first restore happens and then the database promotes and starts a new timeline. Now all of a sudden, the user has to figure out the old timeline id and enter that in to start moving around on that timeline. Is there a better way? E.g. after restoration the database stays in read-only mode until they get to the point they want and then they can certify and promote the database manually?
Thanks!
I am not sure if I understand the question correctly, but the second restore can specify
recovery_target_timeline = 'current'
to remain on the timeline that was active when recovery started.
If a user leaves a comment during a workflow, the comments are duplicated in the workflow comments section by service users for each Auto Advance step I have in the workflow model. Is there some way to not have these steps also create a comment? The Show Non-User Comments toggle doesn't hide these specific workflow comments.
Here's a bit of my workflow where the initiator is requested to make changes and can leave a comment when completing the step:
Here is a comment left by my user a a in the Workflow initiator changes requested step, then duplicated by the service users in the following auto advance steps:
Hi klementine: What you've used above is not an Auto Advancer step, rather a No Operation step. Also, it wouldn't be correct to say that the comments are being "duplicated". The comments are rather being "carried forward". There's a small difference between the two statements here.
By definition a "No Operation" step does nothing. It is simply a placeholder step that will bring the workflow to a halt if Handler Advance checkbox is not checked. The comments are being copied from the previous step because it has been designed that way. The No Operation step is designed to not intervene in the workflow operation and keep the metadata intact. It will not delete any history metadata from workflow node.
Having said that, even if you use an Auto Advancer step, you will experience a similar behavior because the Auto Advancer step is also designed to just advance the workflow to the default next step in cases of OR Splits. It also doesn't alter the workflow metadata.
It's important that we understand the exact business requirement before designing our workflows. I don't feel that a No Operation step is really required in your case.
Is there any way to re run the failed Azure data factory slices by using the powershell cmdlets.
As of now I am re running the slices manually from diagram page. But this is not helping much as I have more than 500 slices and all are scheduled to run on every week.
Just to brief you : 4 days back my database server went down, and all the slices are failed to execute and now I want re run all the slice again.
Also I wanted know, is there any way to get failure notification, if slices failed to execute then I should able to get mail or something so that I can get notified.
Thanks in advance.
You may also try the script mentioned in the link and let us know.
For more information, you may refer the article to monitor and manage Azure Data Factory pipelines.
Last time a similar issue happened to me I ended up using the "Monitor & Manage" tool from the Azure Portal.
You can use the grid view to select your failed slices, and there is a very useful "Rerun" button on the top left corner of the grid.
To get email alerts when a slice fails you can add one using the "Metrics and operations" tool.
The settings is quite well hidden but it exists :)
Whenever the user submits a workflow request from Enterprise portal clicking more than once, multiple instances are generated. Kindly suggest a way to avoid as it is misleading.
Thank you.
Have a look here
In the event this.WorkflowActionBar.EvaluatingCanSubmitToWorkflow you could via the EP's Business Connector session call a static method in X++ to check whether a workflow for your current process / document / whatever already exists and avoid submitting it again. How you determine that of course depends on your environment / process etc.
I'm the beginner of Case and workflow management and want to use OpenText CASE360 create a simple task can anyone advise me how to create/design/implement etc.
first have a local set up of case360.
Choose a POC topic for the same. and start to build the components step by step.
starting with Casefolder, Process, Queries.etc
Start to build components individually and then try connecting each of them.
The help document covers every topic in details