ATE (Import and Export Jobs) System Settings

Dictates cross-list max enrollment behavior.  

The system either uses the largest of the existing values in the group (Maximum)

or combines the values of the group (Summation).

If true, canceled sections are not imported, and existing sections are deleted. If false, nothing is done with them. The default value is true

NOTE:  This setting takes precedence over the ‘import’ option for the IncompleteSectionsImportPolicy.  

Any imported Section that is incomplete AND canceled will be deleted.

Dictates whether or not sections in Astra Schedule should be deleted if not included in the imported data.

NOTE:  Sections that are "skipped" based on the Incomplete Sections setting are not considered missing from the import and therefore are not subject to deletion. The default value is true.

Dictates whether or not section meetings in Astra Schedule should be deleted if not included in the imported data.

NOTE:  Section meetings that are "skipped" based on the Incomplete Section Meetings setting are not considered missing from the import and therefore are not subject to deletion. The default value is true.

If true, SIS room assignments will be ignored on imports.  

New Sections will be created with no room assignments. The default value for this setting will be false.

If true, Astra will drop room assignments during import for any existing Section with a changed meeting pattern.

The default value for this setting will be false.

This setting is used to prevent ATE from deleting cache files associated with ATE jobs when a job completes.  

This can be helpful in circumstances where a job completes without error but an investigation into another issue is still desired.

The default value is false - to delete cache files on successful import.

Prevents the import process from overwriting room assignments on existing, matching sections if the room assignments were modified in Astra Schedule.  

This will prevent scheduling work from being overwritten if the room assignments have not yet been exported back to the SIS.

The default value is "true".If the setting is not otherwise configured in system settings, the spoke will behave as if it were set to "true", meaning that modified room assignments will be preserved during imports.

IncompleteSectionsImportPolicy

(An incomplete Section is any Section that:(1)Has no meetings OR (2)Comprises only Incomplete Meetings         CAUTION:  A Section that is incomplete in the SIS will not be considered incomplete in Astra if the Section has one or more complete SectionMeetings in Astra that do not exist in the SIS (Astra-only complete meetings))

Import = Incomplete Sections in the SIS will be included in the import set and imported as-is. Delete = Incomplete Sections in the SIS will be deleted from Astra,

IF AND ONLY IF the Section is also considered incomplete in Astra AND that Section contains no incomplete Section Meetings protected by the IncompleteSectionMeetingsImportPolicy =

‘import’ setting.Astra-only Sections (those with no SisKey)

or those with an Astra-only Section Meeting are never considered for delete.(The test to determine Section completeness occurs after the processing of DeleteCanceledSections, DeleteSectionsNotInImportSet,

DeleteSectionMeetingsNotInImportSet, and the deletion of any incomplete SectionMeetings.)Skip =

The incomplete Section will be ignored as if it didn’t exist in the SIS. If the Section already exists in Astra, it will not be updated. If the Section does not exist in Astra, it will not be imported.

IncompleteSectionMeetingsImportPolicy

(An incomplete SectionMeeting is any SectionMeeting that:(1)Has no Start TimeOR(2)Has no End TimeOR(3)Has no DaysMetPatternNOTE: StartDate and EndDate are required values for SectionMeetings and therefore are not considered when determining Incompleteness.)

Import = Incomplete Section Meetings in the SIS will be included in the import set and imported as-is. Delete = Incomplete Section Meetings in the SIS will be deleted from Astra

if they exist.Skip =

The incomplete Section/Meeting will be ignored as if it didn’t exist in the SIS.

If the Section Meeting already exists in Astra, it will not be updated.If the Section Meeting does not exist in Astra, it will not be imported.

Specifies how enrollment values are imported from the SIS.UseSection =

The enrollment values in the SIS for the section should be set on all meetings for the section in Astra Schedule.UseSectionMeeting =

The largest value across all of a section's meetings is used for the section.AsImported =

The values for the section and meetings are used as imported.

The PeopleSoft section import spoke supports either single or multi-institution modes.  This system setting determines whether it operates as a single or multi-institution.

The installation/upgrade utility includes a check box on the PeopleSoft connection settings screen that asks if the PeopleSoft data is single or multi-institution, and updates this system setting automatically.  

If the institution has multi-institution data, they will also need to add a system setting with their institution ID.

For Ellucian Banner: This setting determines whether or not Delivery Methods are being imported along with sections.

If true, then the spoke will map a delivery method SISKey (CourseDeliveryMethods.SisKey) from the SIS.

If false, then it is not imported and defaults to "Standard".

The default value is false.