Exercise: Create and Apply a New Work Status
13. Open the properties panel for the Wait shape.
a. In the wait name field type Wait Until Employee Takes Leave.
b. In the Wait Type options select Case Dependency.
c. In the Cases of type field, select Time Off.
d. In the To reach status field, select Pending-Usage.
e. Scroll down and expand Advanced Wait Options. Ensure the Permit End User to
perform check box is selected. The image below can be used to confirm your work.
f. Click OK and then Save updates to the flow.
I got this error message after the Save: Class Key Validation failed for class: Rule-Obj-Class, class key value: Time Off, reason Instance Not Found
Any thought as how do I resolve this issue ?
Pegasystems Inc.
US
I suspect the issue is the entry you are making in 13.c. Could you take a screen shot of the Wait Properties, and post it here?
Also, I am curious about the date stamp on your exercise guide. The second page in the PDF has a Date: at the end of the copyright stuff.
eddie
Lochbridge
US
Not sure what do you mean by the date stamp on my exercise guide passing the copyright??
Lochbridge
US
Pegasystems Inc.
US
Paul,
this looks lilke a copy/paste of the text?
maybe you could just email me the scrren shot - [email protected]
as to the date stamp, look on the second page of the PDF exercise guide. The last thing on that page is a Date: entry.
eddie
Pegasystems Inc.
US
Paul,
than for the screen shot. As I suspected, the entry you are noting in 13.c is not quite right. To be fair, the information provided in the step is a bit misleading.
When selecting for "Cases of type" you have to provide the full context of the case type.
Place your cursor in the field, and then use the down arrow on your keyboard to show the prompt list of available case types. You will want to select the TimeOff case type, but you need to include the full context - as shown in my screen shot.
eddie
Pegasystems Inc.
US
That is the most current publication date. What I did notice is that the individual exercise from the lesson page has an out-of-date version for this particular exercise. I made the necessary notifications to have it updated.
Consider using the full exercise guide from today onward.
eddie
Lochbridge
US
Exercise: Designing an Intent-Driven UI Starting with
Specifications
1. Update the specification for the Change Request flow action (not the entire flow) with the
following changes to reflect the use of controls to guide user input, then save the
specification.
The requestor provides the following information for their time-off request:
Type of Request: Text, drop-down list (allowed values: Vacation/PTO, Family/Medical
Leave, Sabbatical, Bereavement)
Exercise: Designing an Intent-Driven UI Starting with
Specifications
1. Update the specification for the Change Request flow action (not the entire flow) with the
following changes to reflect the use of controls to guide user input, then save the
specification.
The requestor provides the following information for their time-off request:
Type of Request: Text, drop-down list (allowed values: Vacation/PTO, Family/Medical
Leave, Sabbatical, Bereavement)
Date of Request: Date, read-only, automatically calculated
Start Date: Date, calendar
Employee ID: Text
First Name: Text, read-only
Last Name: Text, read-only
Department: Text, read-only
Accrual Rate: Decimal, read-only
Allowed Time Off: Decimal, read-only
Available Time Off: Decimal, read-only
What does it mean by "Update the specification for the Change Request flow action (not the entire flow)"?
Lochbridge
US
I ran my Time Off exercise and passed all the steps in the "Submission" stage but when it arrived at the "Approval" stage, it says the "Requires VP Approval" decision table does not exist. Do I need to create or maybe I did something wrong?
I ran my Time Off exercise and passed all the steps in the "Submission" stage but when it arrived at the "Approval" stage, it says the "Requires VP Approval" decision table does not exist. Do I need to create or maybe I did something wrong?
Save draftOther actions Close