Each Agent in PRISM needs to also exist in Moveware. This allows PRISM and Moveware to communicate which Agents are used on Jobs/Service Orders.

Initial Syncing of Agents between systems

The first step in the integration of Agents between systems is to assign the Parsifal Agent ID to each Agent in Moveware that exists in both PRISM and Moveware. This is the unique ID for the Agent in PRISM. Another important field is the BGRS Group. Each Agent used for BGRS needs to be assigned to the BGRS Group.

This can be done manually i.e. enter the Parsifal ID into the Parsifal field, then Add the Agent to the BGRS Group. Moveware can also assist with loading the Parsifal IDs into Moveware in bulk, using an Excel file.

If an Agent exists in PRISM but not in Moveware, a new Agent will be created in Moveware during the initial sync process. This Agent will be assigned the Parsifal ID automatically.

Adding New Agents and Updating Existing Agents

If an Agent exists in Moveware but not in PRISM, clicking Save on the Agent Details screen will create the Agent in PRISM. This includes new Agents. New Agents should be created in Moveware first.

This also includes any updates to existing Agents. Existing Agents should be updated in Moveware, which will then update PRISM. When the Save button is pressed in Agent -> Details, any Agent that is part of the BGRS Group will send an update back to PRISM to either create a new Agent or update an existing Agent.

In Summary, the initial requirement is to ensure all BGRS Agents exist in both PRISM and Moveware. From that point forward, all updates should be made to Agents in Moveware, which will sync to PRISM.

Parsifal field name	Parsifal Comments	Moveware Field	Moveware Field Description
*supplierKey	GUID provided to suppliers when they begin to use the PRISM Supplier APIs		Pull from backend MoveSupport database
agentID	When sent record will be updated.  When not sent a new record will be inserted.	Agent Details > Agent Settings > Parsifal > Field value
*agentCompanyName		oagents.o-name	Agent Name
agentCompanyCD	Supplier's code for their Agent	oagents.o-code	Agent Code
*agentContactName		oagents.o-contact	Agent Contact
*contactPhoneNbr		oagents.o-phone	Agent Phone
*contactEmailAddress		oagents.o-email	Agent E-mail
*address		oagents.o-add1	Agent Address Line 1
*city		oagents.o-add2	Agent Address Line 2
*adminArea1	State / Province	oagents.o-add3	Agent Address Line 3
adminArea2	Generally County	oagents.o-add4	Agent address Line 4
*countryCD	2 character ISO country code	oagents.o-state	Agent Country Note: If the full country name is entered instead of 2 character ISO code, then the system will look up 'Country' code type from Code Management, find the country with the same description, and use the 2 character code value.
*userEmailAddress	PRISM User Email Address		Pull from 'PrismUserEmail' in Code Management
bookingAgentID	PRISM Number for the Booking Agent, this field should be used by Parent companies adding origin and/or destination agents on behalf of a child Booking Agent		Not Applicable
*lastUpdateDT			Not applicable
*lastUpdatedByFirstName			Not applicable
*lastUpdatedByLastName			Not applicable

---