process a workflow node/activity at a specific date

[norber...@multimageweb.com]

hi workflow funs ;)

after lot of investigation we to understand wf concept.

test scenario: 

1. create document value workflow for c_invoice @created@=@updated@ (i know can use process workflow too..)

2. node 1. start node wait = generate activity = workflow processor run it. (its ok it is only test...how to suspend a node instance)

3. node 2. document action: complete (generate activity complete it) as result invoice will be completed immediately

4. node 3. document action: close 30 days after completion (transition from complete to close when today=+30days) - we use here virtual column "e.. doActionFlag"

in point 4 we lost. why. we found workflow processor processing only activities doesnt generate activities from nodes. means if activity is suspended then its will be processed this looks OK. but the question is: if i want to start the next node after 30 days then. i.)i need to somehow generate the activity and suspend it by transition condition (with due date - how ?) or we need to generate activity from node with a special process at the moment when transition meet our condition  (today=doActionFlag) - then workflow processor process it immediately and close invoice. 

OUR GOAL: at the end we want to define/set a specific date when upcoming activity (node instance) or an existing activity will be processed (FIRE)

generally we dont know in our evalutation phase - how we can suspend an activity (non wait type) - or get it to another status - able processing workflow processor. (complete activity)

what means: start/finish mode. hm...will play will that.. believe others understand well workflows concept.

norbert

This e-mail is confidential and may contain legally privileged information. It is intended only for the addressees and may not be reviewed or used in any way by other recipients. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message and any attachments thereto from your system.

[redhuan d. oon]

I wonder if WF should also integrate or takeover the DocValidate or ModelValidator part because they seem to be doing the same area of concern i.e. manipulating WF. WDYT?

[Heng Sin Low]

#4 is not implemented in the current idempiere workflow module.

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/b4890ad5-d6e7-4184-96fe-38d4b25c5b32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[norber...@multimageweb.com]

Thanks for answers. 

@red1 - i dont know the answer. why i prefer wf is - ability to setup by a consultant/power user. same in like in sf.com. other maybe know the answer.

@hengsin - its important answer. from the bellow concept can you say which approach is better. then i will prepare a design solution proof of concept. who is the best in workflows to decide which concept is better. (push/pull).

norbert

[redhuan d. oon]

You misunderstand a bit my comment. I put in simpler words: I mean WF is better that is why ModelValidator events should be inside it.  :)

[norber...@multimageweb.com]

hi,

i have define a solution design for stated problem here: https://idempiere.atlassian.net/browse/IDEMPIERE-2022

this improvement helps to implement periodic renewal documents by workflow processor. Ideal for contractual and PSA business.

any comment welcome.

norbert