Change Requests are a series of statements and annotations used to configure your Trading Partner accounts.
Document statuses describe where a document is in the overall implementation process. There are eighteen possible statuses. For individual status definitions, see Customer Statuses.
What is a Change Request?
Change Requests are used to request configurations for your trading partners and are fundamental to the onboarding process. An initial request requires you to annotate one or several sample documents to determine what information needs to be extracted from the document and where the information is located. After the initial request, subsequent (or follow-on) requests may be necessary to ensure the document meets your needs and those of your ERP system.
Most Change Requests will be completed prior to moving the trading partner to production, but Change Requests can also be used once a trading partner is live to make additional updates or accommodate small mapping changes.
Initial Change Requests
Initial Change Requests begin the validation process and take the trading partner from the status of New to Configuration Required. The initial request must include all details for mapping, transformations, and business logic.
For the initial request you will be asked to provide at least 5 sample documents, one of which will need to be annotated to show where all required information resides. The sample documents can be uploaded directly to the portal or emailed to the test email address provided by your implementation manager.
- How to Submit Sample Documents
- How to Annotate a Sample Document
If you have First-Pass mapping (FPM) setup, that will be used in place of submitting an initial map request. To learn if FPM is appropriate for you, reach out to your Conexiom representative or Contact Support.
Subsequent Change Requests
Subsequent requests are any requests that follow the initial Change Request and can be made during testing or once the account is in production.
These requests should focus on the changes and should not include all the original request details. If the Connection Developer handling your request has to look for the difference, your requests will take longer and may result in missed changes.
If you are requesting an update to existing logic, then reference a summary of the existing logic and the date it was originally requested. This gives the developer the context they need and helps them see where in the configuration the changes need to take place.
Subsequent change requests can be used for a number or reasons, including the following examples:
-
The trading partner has introduced a new document layout
-
The wrong information from the document is being picked up
-
Changes in the output file require new mandatory fields
-
Hardcoded values in your configuration, such as Bill to or Ship to IDs, need to be updated
How to Submit a Change Request
There are multiple ways to submit a Change Request. While they all have the same end result, some are better suited for certain scenarios.
For an initial Change Request, unless you have First-Pass mapping setup, it is recommended to initiate an email request from the Customer Page of the portal under 'Test Documents'. This will enable you to attach or link to the annotated sample document.
Once an account is in Production, Change Requests can also be launched from the 'Production Documents' tab on the Customer Page.
To submit a Global-level Change Request, i.e. one that will apply to all trading partners, Contact Support. . Global-level Change Requests should only be submitted by individuals with a deep understanding of global logic and its application in change outcomes.