![]() Now quick jump to the PIM artifact and check the result!!…Go-Go-Gadget…Īs expected…A refresh after 30 sec.? Well…What do you think? CORRECT! ✅ Let’s set a delay for 30 sec., save the BPM with a nice name like ‘bpm_delay’ and publish it. Let’s start with a simple BPM and directly add that ‘Delay’ construct and check its properties: The BPMs we create are always saved in a subfolder called ‘bpms’, so our project keeps structured. Make sure the environment is up and running, and you have a project to play along with. So, no time to wait…Let’s go with the flow and… During that journey a saw (again) the ‘Delay’ construct passing by and as my current project also uses it, I thought it was time to gain more knowledge on this nice feature. ![]() Welcome to a new installment of AppWorks tips.Īgain a BPM post!…Why? Well, because last week we played with sub processes and passing messages with data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |