Enrollment 25.5.0.0

Update Submission Records through API

Enrollment supports the ability to update records in the Submission Workspace through the use of a POST /submission/update endpoint within the Enrollment API. This process is supported for Public, Restricted, and Private forms.

This endpoint can be used to programmatically update existing submission records with supplemental information originating from external systems. Using this endpoint can streamline and maintain data consistency between external systems and the Enrollment submission workspace, without a manual export/import process.

This endpoint validates form field names, form field types, list items, checkbox values, maximum length, and format validation, and enforces that a minimal set of data (record ID and workspace ID) is provided. This endpoint does not enforce the satisfaction of required fields nor complex scenario validation, and does allow inserting data into conditionally and statically hidden fields. This endpoint also supports the ability to assign and remove valid workspace tags.

Updating submission records through this endpoint triggers all of the standard downstream processes, if configured and enabled: auto-tagging rules, auto-address verification, calculated fields, field-level change history, submission tag history entries, and so on.

Use of the Enrollment API requires an API Key, which must be generated and provided by PowerSchool Enrollment Support. Use of this POST /submission/update endpoint requires a new permission associated with an API Key, which must be assigned by PowerSchool Enrollment Support.

Approve Submission Records through API

Enrollment supports the ability to approve records in the Submission Workspace through the use of a POST /submission/approve endpoint within the Enrollment API. This process is supported for Public, Restricted, and Private forms.

This endpoint validates the record’s status (Pending Approval), eligibility for approval based on the workspace’s approval criteria, and enforces that a minimal set of data (record ID and workspace ID) is provided.

Approving a submission record through this endpoint updates its Approval History and Approval Date workspace properties, and will trigger approval notification emails, if configured and enabled.

Use of the Enrollment API requires an API Key, which must be generated and provided by PowerSchool Enrollment Support. Use of this POST /submission/approve endpoint requires a new permission associated with an API Key, which must be assigned by PowerSchool Enrollment Support.

Admin - Auto-tagging rules do not create Change History events

When either a Roster Tag Rule or a Submission Tagging Rule was configured to automatically update a form field with a specified value, a field-level change history event was not always created when the tagging rule was executed. This has been resolved. Now, regardless of form type, if the auto-tagging rule changes data items after a record is created (for example, someone manually changes data in the record, which triggers the rule to change data elsewhere in the record, someone manually runs the Re-Apply Tagging Rules task, and so on), then a field-level change history record is created. If the auto-tagging rule changes data items during record creation (for example, importing a record into the workspace), then a field-level change history record is not created.