Another Process Issue

Another Process Issue

  

If i update the Next_Run Column In the outsystems BPM: ossys_BPM_Activity table within outsystem codes, any possible that the current process will be killed and start another new process?


Solution

Hi Xiu xiu,

You really shouldn't mess with the ossys tables. They're fine for reading, but you shouldn't update them unless you are really, really sure about what happens (and even that could break between versions).

Solution

Kilian Hekhuis wrote:

Hi Xiu xiu,

You really shouldn't mess with the ossys tables. They're fine for reading, but you shouldn't update them unless you are really, really sure about what happens (and even that could break between versions).

Ok. noted.

thanks. will ask our team for another solution instead.


Best Regards,

Xiu


Hi Xiu,

If the goal is to stop the current process, you could do several things like a Conditional Start, or a Wait in case you need a time-out or the like.

Kilian Hekhuis wrote:

Hi Xiu,

If the goal is to stop the current process, you could do several things like a Conditional Start, or a Wait in case you need a time-out or the like.

Actually, below is the reason why i need to update it:


we have a product lifecycle, when user creates the product, user also needs put a enddate.

in the product process, we will use the enddate field as the cycle end date.

but  in our application, we also provide a function which we enable user to update the the enddate attribute.

in current logic, we do nothing to the process, process will stop when it reaches the end date.


this is the story.