Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Hi guys,
I've been trying for more than 1 month this feature in the Cloud version of Joget, but with no luck.
I did tried from the complex to the simple way and there is no deadline triggered.
Look this simple example:
Roles in the proccess above: Applicant, Approver, System.
In "Completition" Activity deadline is set: Async, Minute, 5, DEADLINE
In transition the setting is: (no name given), Exception, DEADLINE
In General Settings, Process Deadline Checker Interval: 180
Am I missing something else? because this is not working.
Here is the running process details:
TIA.
13 Comments
Hugo
Hi there,
I just tried to modify default HR Expenses Claim App that comes by default in cloud account and it worked as expected.
Can you attach your app here for us to inspect?
Thanks.
Francisco Muro
Hi Hugo, in my last test, defining 5min. as deadline limit it worked sending the expected email after close to 5 hours, IDK why! So, IDK how much time should I wait if I set limit to 1 day...
Here is attached the app...APP_tasks-2-20141029014824.zip
I want it sending email messages until user finish the activity (Sending Reminder Repetitively).
Regards
Hugo
Hi there,
1.Your deadline is set up correctly. I don't see why it does not work.
The deadline checker will runs at interval picking up matured/lapsed deadlines and executes them accordingly.
2. By looking at your design, every time your "Email on Pending" executes, it will create a new activity. I don't think that's what you want. Please see Sending Reminder Repetitively.
Hope this helps. Thanks.
Francisco Muro
Good morning Hugo.
I tested the zip App sent to you and I got notification at 3:03am (exactly same time as my frist post test when I though got notification after 5hrs). And, as you can see the deadline limit is set to 5 minutes and 1 minute in the zip App. Something is wrong here!
I'll create a dummy activity to cover what you say in number 2. (My 1st design was like this example but I had no luck and was testing different ways to try norrow my problem).
Hope your feedback.
Regards!
Francisco Muro
This is how I first tested my App with no success; APP_tasks-2-20141029140523.zip (just tested today again, and, after 30min, I get no email message).
Another question, If I have a date variable "startreminder" and would like to define something like this;
startreminder > today && status != "Approved" && status =! "Rejected"
How should I compare dates here?
TIA.
Julian
Hi Francisco,
Are you using the Office Working Hour Deadline Plugin? If you are, then the deadline takes only business hours into account. For example, if it's during the designated non-working hours then the deadline will only be triggered when the next business hours resume.
Best Regards
Julian
Francisco Muro
uhmm yes, I'm using it! thanks for let me note!
Seems that Joget plugin is not taking into account my "User Profile" "Time Zone"...
TY!
Francisco Muro
I LOL because all my tests are at night, feeling dumb! sorry.
If the email was sent at 7 am my time could figured it out.
Hugo
Hi there,
I have just tested locally and the deadline is triggered in a timely manner within minutes. Perhaps you can check on what Julian commented.
In a related case, I would like to point out that the transition after "Email on Pending" to "Wait for timeout" will not work. This is because "Wait for timeout" already exists therefore no new activity instance will be created again, and therefore, no new deadline will be triggered again.
Solution is simple. Since your intent is to send out reminder repetitively, simply set the deadline execution mode to "synchronous" so that the pending "Wait for timeout" activity will be terminated and will be created again after "Email on Pending" finish executing.
Francisco Muro
Many thanks Hugo, I'll set it to "synchronous" :)
I understand how sync/asyc works now.
Francisco Muro
Hugo, check this question please
startreminder > today && status != "Approved" && status =! "Rejected"
About how to compare dates, regards.
Hugo
Hi there again,
1. Both will need to be existent workflow variables.
2. This will compare character by character which I don't think you want it that way. All variables are stored in string type so you will need to cast them accordingly to its appropriate format first.
In case you do not know already, you may use your browser (i.e. firefox) 's debugger console (or firebug as shown in the screenshot) tp try to compose the condition expression and test it out first before putting them in your workflow designer.
I believe you should use != instead of =!.
Hope this helps.
Cheers.
Oz Boo
I wonder who will be assigned as the performer of the activity "Wait for timeout" in this case?