I posted the question of this topic and the AI response was provided below. Can someone please verify this is correct and provide further details and a contact person at FSM Cloud Hosting.
Will be greatly appreciated!
Summary — recommended packaging and handover checklist for FSM 6 deliveries to FSM Cloud team
1) Package source and artifacts
- Export all deliverables from your local FSM 6 environment:
- Solution packages/customizations (code, DLLs, compiled artifacts).
- Workflow/BPMN files and any process definitions.
- UI/Studio artifacts, JourneyApps or mobile app packages if used.
- Database migration scripts (schema changes, seed data).
- Configuration files (connection strings, feature toggles) with placeholders for secrets.
- Integration artifacts (API specs, mapping files, middleware connectors).
- Test artifacts (unit/integration test suites, test data, automation scripts).
2) Version control and manifest
- Commit everything to a Git repository (one branch per delivery or a release tag) so history and versions are traceable.
- Add a release manifest (JSON or YAML) that lists files, versions, required order of deployment, and any dependencies.
3) Packaging format
- Produce a single deployment bundle (zip/tar) containing:
- /artifacts (binaries, packages)
- /db (migration scripts)
- /config (templated configs)
- /workflows (BPMN / process files)
- /integrations (connectors, API specs)
- /tests (automated tests)
- manifest and release notes
- Include checksums for large artifacts to ensure integrity.
4) Environment and configuration separation
- Use templated configuration with environment variables/placeholders rather than hard-coded values so the Cloud team can inject production settings.
- Provide a clear mapping of which config values must be provided by the Cloud team (e.g., credentials, endpoints, resource sizes).
5) Deployment automation (recommended)
- If possible, include CI/CD pipeline definitions or scripts (Jenkins, GitLab CI, Azure DevOps) that demonstrate the expected deployment steps (build → package → DB migrations → smoke tests).
- If no pipeline is available, provide clear step-by-step deployment scripts and the exact order of operations.
6) Validation and rollback
- Include a deployment validation checklist and automated smoke tests that the Cloud team can run post-deploy.
- Provide rollback scripts or instructions to revert DB changes and application artifacts if required.
7) Operational information and runbook
- Provide release notes covering:
- What’s included and purpose of changes
- Any DB schema changes and required downtime windows
- Known limitations or manual post-deploy steps
- Provide a runbook with:
- Pre-deploy checks
- Step-by-step deploy actions with expected outputs
- Post-deploy verification steps
- Escalation/contact details and component owners
8) Handover package contents checklist (deliver to FSM Cloud team)
- Deployment bundle (zip/tar)
- Git repo URL + branch/tag (or repo snapshot)
- Manifest and release notes
- DB migration scripts
- Config templates and mapping table for environment values
- CI/CD pipeline definitions or deploy scripts
- Automated smoke/regression tests and instructions to run them
- Runbook and verification checklist
- Contact list for owners, subject-matter experts, and tests’ authors
9) Practical notes from similar FSM 6 usage
- FSM 6 customers commonly integrate external tools (mobile apps, scanning devices, Power BI) and rely on IFS business rules to drive logic; ensure those bindings and integrations are included in the package.
- Where the cloud product differs (for example in reverse-logistics support or automated deployment processes), clearly call out any features that require Cloud-side handling or additional Cloud capabilities.
Note: The documentation provides partial information on this topic.
