Using the Write-back Mode in Application Designer AI Assist
When the developer selects the Enable write-back mode check box in the PeopleCode Assist Settings, the system allows LLM-generated and modified PeopleCode to be saved to the PeopleSoft database.
When write-back is enabled, the system marks all PeopleCode object files in the project context cache as write-enabled, allowing the LLM to modify these PeopleCode object files directly. See Setting the LLM Client Plugin File.
Note:
Each write-back command should start with a#, for example, #Commit.
#HelpThe commands listed below let the developer save the LLM changes to the PeopleSoft database.
| Command | Description |
|---|---|
|
Compiles and saves all modified PeopleCode to the database. Each successful commit also adds the modified PeopleCode files into an internal Commit Cache, enabling you to restore from a specific commit, if required. |
|
Rolls back all the commits made during the current chat session. This means all the changes saved to the PeopleSoft database, for the commits done during the chat session, are reverted. |
|
Lists all commits made during the current chat session. |
|
Restores the changes from a selected commit. Restored changes are compiled and saved to the PopleSoft database. |
|
Displays the differences between the baseline PeopleCode (the version stored in the PeopleSoft database when the chat session began) and the PeopleCode saved in a selected commit. You can also use this command to compare the PeopleCode saved in any two commits. |
|
Compares the PeopleCode saved in commit_message 1 and commit_message 2. Note: Close the Diff window after you view or edit the PeopleCode. |
|
Compares the baseline PeopleCode and the latest PeopleCode generated by the LLM. You can also use this command to edit the generated PeopleCode for any compilation errors. Note: Close the Merge window after you view or edit the PeopleCode. |