Lifecycle process
Artifacts have several lifecycle stages ranging from being merely a candidate through development, implementation, and eventual deprecation and reuse. Each stage has own specific features and each organization has different detail requirements for these different stages.
The stages can be divided into development and runtime stages and before a service can be allowed to move from one stage to another, all necessary policy requirements and approvals must be in place. In Systinet lifecycle, administrator defines the processes, given policy, task and approvals.When all the requirements and tasks are complete, the artifact owner makes a request to move the process to the next stage. If the administrator has assigned approvers, they are notified and are required to vote on approval. Depending on transition type, the governed artifact moves to the next stage and the lifecycle automatic actions defined for these stages are triggered.
Artifacts that progress through a governance lifecycle together are grouped together in Systinet in a structure called a Lifecycle Tree.
Policy Management
Systinet enables you to validate your Catalog content against published policies to ensure its consistency and conformance to your business policy.You can use the Policy Report feature of the Reports tab to perform ad-hoc manual validation.
You can associate runtime policies with SLO artifacts that are linked to contracts. Once the contract is deployed it’s associated policies are configured into the proxy object created for the contract.
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
Overview of governance management in HEP Systinet.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox
