Skip to content

NIM update for v6.3.2 #420705 #438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
paigeyoung-netwrix wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

NIM update for v6.3.2 #420705 #438

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/identitymanager/current/integration-guide/ui/producttranslations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ sidebar_position: 10

This topic shows how to import product translations into Identity Manager. A product translation means a translation of a Identity Manager's component, for example a button display message, not the translation of a configured component.

Currently in preview mode, Identity Manager supports both left to right and right to left languages. Use the toggle on the Settings Page to activate right to left languages.

## JSON Translation File

The translations are given to Identity Manager in a JSON file, through the configuration deployment tool. This section first explains how to write the JSON file, then how to use it with the deployment tool.
Expand Down
4 changes: 2 additions & 2 deletions ...ent/user-guide/set-up/provisioning-rule-creation/scalar-property-computation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
---
title: "Compute a **scalar** Property"
description: "Compute a **scalar** Property"
sidebar_position: 20
Expand Down Expand Up @@ -111,7 +111,7 @@ synchronize the property back to Identity Manager; **Create Only** to use this c

For example, consider a system, that we want to connect to Identity Manager (let's call it SYST) using a title property. Consider also that SYST needs to be provisioned with the value of title, but does not allow any other system to retrieve said value.

In this case, we use **Create Only** so that Identity Manager sends the adequate provisioning order upon creation, and then is able to change the provisioning state to **Executed** without synchronization. If any changes impact that ****scalar** Property** value the workflow state will be modified to **PolicyApprovedWithChanges** meaning that the policy value is not equal to the external system's value and that will not be provisioned.
In this case, we use **Create Only** so that Identity Manager sends the adequate provisioning order upon creation, and then sets the provisioning state to **None** without synchronization. If any changes impact that ****scalar** Property** value the workflow state will be modified to **PolicyApprovedWithChanges** meaning that the policy value is not equal to the external system's value and that will not be provisioned.

- Comparison type: Comparison type between the value of the target object computed by the rule and
its value from the managed system. Non-conforming values are displayed on the **Provisioning Review** screen.
Expand Down