What should the checklist establish?
The goal is to identify an actual prerequisite rather than rely on 'we use the cloud'. Record Simphony Enterprise, POS client and, when relevant, Reporting and Analytics versions separately. The POS terminal release may differ from the enterprise release.
Record the release and service model
Ask the authorised venue administrator or provider for the Enterprise release, POS client release, R&A release and cloud delivery arrangement. When an authorised Configuration and Content API account exists, Oracle's getReleaseVersions operation can return the Enterprise and API releases.
That endpoint is not a public, anonymous version checker. Without the required C&C subscription and permissions, request the information from the service provider.
Choose the appropriate API
Evaluate STS Gen2 for supported check and transaction operations, BI API for analytic or bulk data needs, and Configuration and Content API for configuration access. Oracle excludes bulk transaction retrieval and general reporting from intended STS Gen2 use.
Verify account administration and access scope
An authorised user with Manage API Accounts permission can use Administration > System > API Accounts. The STS Gen2 account has a Cloud/Local/Both client scope and a separate location authorisation scope.
Confirm that the account is active and limited to the required outlets. Do not circulate passwords, tokens or secrets in normal support email.
When the client and Enterprise releases differ
The release shown on a POS terminal can differ from the Enterprise release returned by an authorised Configuration and Content API call. That is not automatically a fault. Record both separately and ask the provider to confirm the supported release combination for the intended STS Gen2 workflow.
Do not assume a head-office release applies to every outlet when configurations vary. Verify the actual pilot location, revenue centre, workstation references and API permissions. Successful authentication does not prove that the desired POS operation has succeeded.
- Record Enterprise and POS client releases separately.
- Distinguish API entitlement from account permission.
- Identify the pilot outlet and revenue centre.
- Record an owner and reply date for every open question.
Produce a decision record
Record the venue, versions, delivery model, API type, subscription state, administrator, authorised locations, extra licence or upgrade needs, and date of written confirmation. Identify missing items as licensing, technical or permission blockers.
If the provider has not supplied these facts, use the integration information request template. Do not run live transaction tests until the prerequisites are confirmed.
