System Architect Essentials (8): Capstone exercise - US-109 instruction to remove parameter causes a fatal save error
I am currently unable to continue the exercise because of the following issue. Following this instruction from the “Technical Approach” causes a fatal save error:
- Switch to Dev Studio and modify the Savable Rental Customer data page to:
- Remove the pyGUID parameter.
The attached file shows from where I tried to remove this parameter, and the resulting error message. It does seem odd to me that we'd want to remove a unique identifier; wondering if there might be a copy-and-paste error in the instructions.
Pegasystems Inc.
US
Elmer
I believe you are receiving this error due to the fact you saved the rule right after removing the pyGUID parameter. Please try the following steps to implement US-109:
Follow these steps to persist new customer information to the Pega Customer system of record.
Connect the Rental Customer data type to a Pega system of record
1. In App Studio, from the left navigation panel, select Data to open the Integration Designer landing page.
2. From the Integration Designer landing page, select the Rental Customer data type
3. Click the Data views tab.
4. Click Connect to system of record
5. Click Next to accept Pega as the system of record and generate three Data views
Elmer
I believe you are receiving this error due to the fact you saved the rule right after removing the pyGUID parameter. Please try the following steps to implement US-109:
Follow these steps to persist new customer information to the Pega Customer system of record.
Connect the Rental Customer data type to a Pega system of record
1. In App Studio, from the left navigation panel, select Data to open the Integration Designer landing page.
2. From the Integration Designer landing page, select the Rental Customer data type
3. Click the Data views tab.
4. Click Connect to system of record
5. Click Next to accept Pega as the system of record and generate three Data views
Modify the Savable Rental Customer data page
1. Switch to Dev Studio, and from the left navigation panel, select Data types > Rental Customer > Savable Rental Customer.
2. Select the Parameters tab.
3. Under Parameters click the trash icon to delete the pyGUID parameter.
4. Click the Definition tab.
5. Under Data sources, from the Source drop-down, select Data Transform.
6. In the Data transform name field, enter PersistNewCustomer.
7. To the right of the Data transform name field, click the crosshairs icon to create the new data transform.
8. On the new rule form, click Create and open.
9. Click the Pages & Classes tab
10. In the Page Name, field enter pyWorkPage.
11. In the Class field, enter or select Tour-CarRentals-Work-RentalReservation.
12. Click the Definition tab.
13. In the first set row, in the Target field, enter Top.
14. In the Source field, enter pyWorkPage.RentalCustomer.
15. Click Save to save to save your changes.
16. Close the data transform rule.
17. Click Save to save the changes to the data page.
Add a new automation step
1. From the left navigation panel, click Case types > Rental Reservation to open the case type workflow.
2. Under the Create New Customer process, click + Step > More > Automations > Save data page > Select to add a new automation step.
3. In the step label, enter Save New Customer to name the new step.
4. Click and drag the Save New Customer step before the Account Setup Confirmation email step.
5. Select the newly repositioned Save New Customer step. The property panel is displayed on the right.
6. In the Data Page Name field, enter or select D_RentalCustomerSavable.
7. Click Save to save the changes.
Verify your work
Click Save and run to create a new case.
Click Submit to advance the case to the Collect Customer Information step.
Enter valid data and click Submit to advance the case to the Verify New Customer step.
Approve the step to automatically advance the case to the Enter Rental Information Step.
From the left navigation panel, click Data types > Rental Customer.
Click the Records tab and verify the customer information entered in the case is saved as the first record.
Please let me know if this resolves your issue,
Sean
Pega Academy Self-Study Support Team
Excellus Health Plan Inc
US
Hi Sean. This is very close. The errors are gone, but it is saving a blank record instead of one with the data. There has to be a plumbing issue somewhere. What should I check?
---
There were two things that I initially did in a different order:
1. I created the new automation step first. I don't think that made a difference, though, as I needed to specify the data page name after creating it anyway. I did that because I've had problems triggered by objects not being created yet when I've done other parts of the capstone exercise.
2. What did make a difference was I saved immediately after deleting pyGUID, which now appears to be the wrong thing to do. I waited until after the end, and that eliminated the errors.
Booz Allen Hamilton
US
I had the same issue -- saving blank records (the whole row is blank) instead of user input. I got it solved by configuring my view. Before I had the Collect Customer Information view set as a combination of 4 fields: Personal information, Address information, Licensing information, and Issuing Authority. Instead, you should delete all four fields but add your Rental Customer field, that's it.
Since when we set Top = pyWorkPage.RentalCustomer in data transform, we are telling pega to copy the user input value of their first last name, email, phone, address, license info, etc from pyWorkPage and paste to savable data page. RentalCustomer != personal info + address info + licensing info + issuing authority. Even though essentially they are representing the same fields. Since property names are not the same, the value user put in under First Name under personal info won't be transferred to RentalCustomer automatically. Kind of confusing... Just remember, if you tell pega to copy from pyWorkPage.A, then user must enter value within property A, otherwise the record would be blank.
Capgemini India PVT Ltd
IN
Thanks a lot..it worked :-)
Cognizant Technology Solutions India PVT Ltd
IN
No data is being stored. It is telling
No data is being stored. It is telling
Banco M?ltiple Bhd Le?n SA
DO
Hello Hedes, I have followed your steps and doing the tests I see that in the end I do not have the expected results in the data record, can you help me to review what happens?Hello Hedes,
Accenture Technology Private LTD
IN
Thanks so much sir ……..
Excellus Health Plan Inc
US
Unfortunately, because of a glitch that happened later in the exercise, our systems folks had to recreate my virtual machine from scratch. I followed the above procedure to redo US-109, but now I'm not even saving the blank record any more. I'll attach a file showing what I have, named 20190405 US109.jpg.
Excellus Health Plan Inc
US
I think I need to insert the new data transform (PersistNewCustomer) in the process, as shown in the attached file (20190409 Missing Data Transform.jpg), but it doesn't appear in the list. If that is correct, how do I make it appear in the list? If that is incorrect, what else do I need to do?
Updated: 23 Apr 2019 22:42 EDT
Comture Corporation
JP
As I had the same error, I set as directed, but the data was not saved.
Looking at the clipboard viewer
The following error was displayed:
There is 1 error
Unable to load data page D_RentalCustomerSavable. Required parameters: UserName. Can not be blank
Please tell me how to resolve this.
Cognizant Technology Solutions India PVT Ltd
IN
I followed the same steps, but the data is not being stored in the records of the database.
When i click on Dev studio > Data Types > Rental Customer > Records Tab it is showing no columns to display. I have followed the same steps that you have mentioned. I am new to pega.
Infosys Ltd
GB
Hi,
I was wondering if anyone was able to complete US-109? I have followed the steps above, after saving no errors showed however I have also got the problem where it doesn't save to the record. I am on Dev Studio, I click Data Types, then I click the icon next to 3 with a circle in it to see the records that should be stored in there however it shows "There are no columns to display".
I have checked the clipboard and I can see pyWorkPage has all the data from where a new customer enter all their details (From Collect Customer Information step). I have also configured the extra step to happen before sending the email, save data page that has D_RentalCustomerSavable inside data page name.
Thanks,
Pegasystems Inc.
US
Same issue here.
Deutsche Telekom Services Europe
DE
Hi,
i also get stucked at US 109 and dont know how to get it working with saving the Customer data. No record after some tests and no idea how to solve this.
Did someone get it fixxed? Pls tell me :)
Thank you!
Pegasystems Inc.
US
Attached is the step by step with images.
Hope this helps,
Sean
Pega Academy Self-Study Support Team
Banco M?ltiple Bhd Le?n SA
DO
Hello Hedes, I have followed your steps and doing the tests I see that in the end I do not have the expected results in the data record, can you help me to review what happens?Hello Hedes,
You Can help me please, I Want to Complete that exercise.
Deutsche Telekom Services Europe
DE
Thank you for your quick reply. I have already configured everything like in your step by step instruction.
Cant find any mistake. My Wording is a little different to yours but all in all it should be the same configuration as mentioned.
I have prepared some screenshots in the attachments
Can you find my mistake? Thank you
Commonwealth Bank of Australia
AU
Hi everyone,
I also had issues when it came to completing US-109. It appears the problem may relate to how the fields have been defined i.e. the fields have been defined in separate field groups - Personal Information, Address information, Licensing information and Login credentials and these 4 field groups have in turned been referenced within the Rental Customer field group.
I was informed by Pega Academy (I emailed them separately about running into issues with US-109) that the fields need be created in a non-hierarchical flat structure i.e. all individual fields are created in the Rental Customer field group.
Because there was a lot of re-work involved due to this error, I started from scratch with the user story, US-104 being corrected and from there I haven't had any issues since.
Hope this helps!
Bank of America
US
Hi, I figured that out, but the code is till not saving the data. Thanks.
Kaiser Permanente Health Care
US
Thank you. I made the exact mistake!
Regards,
ING
NL
The instructions are so misleading. The statements in the exercise are not even consistent. Really bad!!!!!!!!!!!!
Sky Solutions LLC
US
Hello,
Is there an alternate way to fix the issue without having to start from the beginning of the Solution Build?
I also initially created separate field groups for each "group" (I.e. personal information, address information, etc.) referenced within the Rental Customer field group.
Instead of starting from the beginning, I re-configured the Collect customer information step view with only the Rental Customer field group and individual fields (I.e. first name, last name, etc).
Although, there are still no columns to display in the Records tab after following the steps above. I am sure there are ways to debug/test, although I am stumped on where to begin/what to be looking for. I am thinking it is a mapping issue.
Does anyone have any suggestions on what to look for/where to begin to debug?
Thank you!
Sincerely,
Regina
Deutsche Telekom Services Europe
DE
Hi,
thank you @JudyK for this advice.
I had already thought about this, but then discarded, cause the US exectly tells how to create the data class with field groups. I will try it with your advice and hope that i can continue with the other 14 UserStories :D
I will let you know if it works for me!
Bank of America
US
Hi, the data are not being saved. Additionally, I can navigate to the following error in the Actions dropdown. I hope someone explains how to fix it.
CGI
NL
I had the exact same error message (Improper usage of the choose best ruleset api [..])
The cause was that my RentalCustomer data type was created on the wrong level (that is my guess anyway - I am new to Pega). I could see the data type in App Studio with the Case Type on the Data Model tab but not under Data or in Dev Studio under Data types.
So to fix it I made a new datatype Customer directly from Data and repeated all steps up from US-104 replacing RentalCustomer with Customer.
As noted before it is also crucial to have all properties directly under (Rental)Customer. Only the view is divided in sections not the data type itself. (US-104)
Cognizant Technology Solution
GB
Hello,
As per your statement -- "As noted before it is also crucial to have all properties directly under (Rental)Customer." could you please confirm if you mean all the scalar property like FirstName , City , PostalCode, etc are to defined under the Tour-CarRentals-Data-RentalCustomer class ?
Also in the Data Transform used in the D_RentalCustomerSavable data page , we set Top = pyWorkPage.RentalCustomer as per the instructions.
However, we are not setting those individual scalar properties under the RentalCustomer class in this Data Transform. Will it save the RentalCustomer class instances ? Is there anything else that need to be done ?
Cognizant Technology Solution
GB
The following setup in the Data Transform successfully saves the record via Savable DataPage automation :-
