Differences

This shows you the differences between two versions of the page.

--- devel:documentation:roles:adm:role_assignment [2019/07/23 11:37]
svandav [Running state]
+++ devel:documentation:roles:adm:role_assignment [2019/07/26 13:44]
svandav [System state]
@@ Line 90: / Line 90: @@
 ====== System state ======
+{{tag>system state request}}
 The role request has a status item that identifies whether the request has already been executed. The **Executed** state in this case means that the request has been approved and the changes have been executed in IdM. **This state only reflects the state in IdM**.
@@ Line 98: / Line 100: @@
 ==== Running state ====
+{{tag>virtual}}
 Some of the provisioning operations is not completed.
@@ Line 112: / Line 115: @@
 {{ :devel:documentation:roles:adm:request-inprogress-on-vs.png?800 |}}
+If the request contains **pannding virtula system requests**, the 'status on the systems' will be set to executed only if all virtula system requests will be **resolved**. This means that they will either be successfully approved or will be rejected by implementer. If the virtual system request is rejected, the status on the request item will be set to **CANCELED**.
+{{ :devel:documentation:roles:adm:request-detail-canceled-on-vs.png?800 |}}
 ==== Failed state ====
@@ Line 145: / Line 152: @@
 ==== Not executed state ====
 This state is **very similar to the case when the provisioning operation is blocked**. Occures where system is seta to **read only** mode.
-===== Link to request from a provisioning operations =====
+===== Link to request =====
 **In the provisioning operations agenda**, all operations that were created under a given request have a link to that request (**key icon**).
 {{ :devel:documentation:roles:adm:provisioning-operation-key.png?800 |}}
+**Similarly in the agenda of virtual system's requests**, all requests that were created under a given role request have a link to that request (**key icon**).
+{{ :devel:documentation:roles:adm:request-on-vs-key.png?800 |}}