Configuration
Configuration builds the signed design in the target system. The agent plans the changes, applies them after your approval and records every setting it changed.
Configure the sandbox
Section titled “Configure the sandbox”- Give the agent the signed design and the sandbox connection.
- Ask for a configuration plan.
- Review the plan.
- Let the agent apply it. Before the first write, the agent asks once for the permissions the plan needs.
How the agent configures each system
Section titled “How the agent configures each system”- NetSuite: Custom fields, record types, forms, workflows and scripts deploy through SuiteCloud. See NetSuite configuration.
- Acumatica: Setup screens such as payment terms, numbering sequences, preferences, users and roles become available through a custom endpoint. See Acumatica configuration.
- Sage Intacct: Module preferences, dimension settings and terminology change through a ready-made tool that plans, applies and verifies each change. See Sage Intacct configuration.
- Other systems: The agent configures through the system’s API where the API exposes the setup. Ask the agent to list the settings that the API does not expose as manual steps in the plan.
Record what changed
Section titled “Record what changed”Ask the agent for a configuration workbook that lists every setting it changed. It saves the workbook as an Excel artifact in the project, so you can hand it to the client.
Repeat in production
Section titled “Repeat in production”After the client accepts the sandbox, repeat the same configuration in production with the production connection. Give the agent the configuration workbook from the sandbox, so production gets exactly the accepted settings.
Then continue with Testing and UAT.