Thank you to everyone who joined today’s IFS Cloud New Customer Enablement webinar. We received some excellent questions during the session, and we've captured both the questions and answers below:
1. With an evergreen model, how are customers keeping up with regression testing for major releases?
Answer:
- Customers can use the Lifecycle Experience Center (LEC) to test new releases before committing them to their live environments.
- New releases can be deployed into test environments where they can be validated against the customer's existing customisations and configurations.
- Many customers take some time after a release becomes generally available to perform testing before adopting it.
- Upgrading immediately is not mandatory, as each release remains supported for approximately two years from general availability, allowing customers to remain on a stable release while continuing to receive service updates.
2. It looks like the Build Place is really more of a code repository/merge environment and not used for any functional testing of the application. Is that correct?
Answer:
- No, while the Build Place is commonly used for code repository management, branch merging, and update validation, it can also be used for functional testing.
- Developers and administrators can spin up temporary development and test environments on demand for functional testing purposes.
- These environments can be created from specific repositories and branches to validate changes before deployment.
- The environments are temporary and are not intended for storing customer data permanently.
3. Can deliveries be set up to require approvals in LEC? For example, a developer/admin triggers a delivery, but it requires approval from management or a director. Or is that approval expected to happen outside LEC?
Answer:
- The host was not aware of a built-in workflow that requires approval for all deliveries.
- Delivery capabilities are controlled through role-based permissions within LEC.
- Only certain roles, such as Administrators and Technicians, are permitted to create and execute deliveries.
- The recommended control mechanism is to assign users the appropriate role and permissions rather than relying on an approval workflow.
- Administrators do have delivery override and cancellation capabilities.
- Formal management approval processes would generally need to be handled outside of LEC.
4. Question: Who assigns users to the LEC portal for the different studios?
Answer:
- The customer administrator is responsible for assigning users to the Lifecycle Experience Center – refer to this knowledge article for full details:
Customer Feedback Raised
A customer provided feedback that part of the presentation felt like a promotion of Cloud Services and was less relevant because they were already Cloud Services customers.
This feedback was acknowledged and will help improve the content of future webinars.