Exceptional Handling with Repository APIs
Hi Team,
We are in a process of converting Connect File Implementations to Repository APIs.
Currently Implementation is as below:
- Loop through a list and then open a file only at the first index of the list
- For the subsequent iterations , we keep on updating the same file by calling the connect File method in APPEND file mode
- For Exceptional Handling if at the time of appending the record to the file we get Step status Fail we update Failure Status for that record in main table so that it can be picked and tried in next run
While moving to Repository API
- There is no provision to open the file and append a record one by one therefore we are creating a String-Buffer-Append Object and using the same we create the file once
How can we handle the Exceptional Handling with Repository apis
Infosys
IN
If anyone has a clue kindly respond
Pegasystems Inc.
GB
To handle exceptions while converting Connect File implementations to Repository APIs, you can follow these steps:
- Loop through the list and create a StringBuffer object to store the file content.
- For each iteration, append the content to the StringBuffer object.
- In case of an exception during the appending process, update the Failure Status for that record in the main table so that it can be picked and tried in the next run.
- After completing the loop, convert the StringBuffer object to a String and use the Repository API to create or update the file in the repository.
By following this approach, you can handle exceptions while appending records and ensure that the file is created or updated in the repository only once, after all records have been processed.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy:
File getting corrupted when Connect-File method is being used > Chunk 0
CONNECT REST- Error Handling across the application-Design query > Chunk 0
To handle exceptions while converting Connect File implementations to Repository APIs, you can follow these steps:
- Loop through the list and create a StringBuffer object to store the file content.
- For each iteration, append the content to the StringBuffer object.
- In case of an exception during the appending process, update the Failure Status for that record in the main table so that it can be picked and tried in the next run.
- After completing the loop, convert the StringBuffer object to a String and use the Repository API to create or update the file in the repository.
By following this approach, you can handle exceptions while appending records and ensure that the file is created or updated in the repository only once, after all records have been processed.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy:
File getting corrupted when Connect-File method is being used > Chunk 0
CONNECT REST- Error Handling across the application-Design query > Chunk 0
Read File from FTP Server > Chunk 0
In Order to fetch records from a DB table is it necessary for the record to be open First? > Chunk 0
Infosys
IN
Pegasystems Inc.
GB
@ShwetaB96 many thanks for your feedback.
Our main documentation about Repository API's (Pega 8.8) can be found here and here.
Feel free to use the 'Feedback' button against our documentation articles if you feel they lack any level of important detail.
Infosys
IN
Have raised the feedback , what are the next steps to follow the same
Pegasystems Inc.
GB
@ShwetaB96 please have a look at the limitations listed in Using repository APIs in your application
@nvkap is this something you could comment on?