From 5015b6de177265aa575f96d0df6b43bb20c098cd Mon Sep 17 00:00:00 2001 From: Martin Lizner Date: Fri, 3 Jun 2016 14:07:05 +0200 Subject: [PATCH 1/5] Fixing MID-3084 --- .../src/main/resources/localization/schema.properties | 8 ++++++++ .../com/evolveum/midpoint/report/impl/ReportUtils.java | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/infra/schema/src/main/resources/localization/schema.properties b/infra/schema/src/main/resources/localization/schema.properties index c3120a8314c..56226db53b2 100644 --- a/infra/schema/src/main/resources/localization/schema.properties +++ b/infra/schema/src/main/resources/localization/schema.properties @@ -85,6 +85,14 @@ AuditEventTypeType.WORKFLOW_PROCESS_INSTANCE=Workflow process instance AuditEventTypeType.WORK_ITEM=Work item AuditEventType.WORKFLOW_PROCESS_INSTANCE=Workflow process instance AuditEventType.WORK_ITEM=Work item +OperationResultStatusType.FATAL_ERROR=Fatal Error +OperationResultStatusType.HANDLED_ERROR=Handled Error +OperationResultStatusType.IN_PROGRESS=In Progress +OperationResultStatusType.NOT_APPLICABLE=Not Applicable +OperationResultStatusType.PARTIAL_ERROR=Partial Error +OperationResultStatusType.SUCCESS=Success +OperationResultStatusType.UNKNOWN=Unknown +OperationResultStatusType.WARNING=Warning BeforeAfterType.AFTER=After BeforeAfterType.BEFORE=Before Boolean.FALSE=False diff --git a/model/report-impl/src/main/java/com/evolveum/midpoint/report/impl/ReportUtils.java b/model/report-impl/src/main/java/com/evolveum/midpoint/report/impl/ReportUtils.java index bc6f620b0dd..f0ca2107c2f 100644 --- a/model/report-impl/src/main/java/com/evolveum/midpoint/report/impl/ReportUtils.java +++ b/model/report-impl/src/main/java/com/evolveum/midpoint/report/impl/ReportUtils.java @@ -174,7 +174,7 @@ public static String getPropertyString(String key, String defaultValue) { String val = (defaultValue == null) ? key : defaultValue; ResourceBundle bundle; try { - bundle = ResourceBundle.getBundle("localization/Midpoint", new Locale("en", "US")); + bundle = ResourceBundle.getBundle("localization/schema", new Locale("en", "US")); } catch (MissingResourceException e) { return (defaultValue != null) ? defaultValue : key; //workaround for Jasper Studio } From 6c25d0a337d1156b5394beda909d8defc8187f40 Mon Sep 17 00:00:00 2001 From: Martin Lizner Date: Fri, 3 Jun 2016 14:46:44 +0200 Subject: [PATCH 2/5] MID-3084: removing locales that duplicates with schema --- .../src/main/resources/localization/Midpoint.properties | 8 -------- 1 file changed, 8 deletions(-) diff --git a/gui/admin-gui/src/main/resources/localization/Midpoint.properties b/gui/admin-gui/src/main/resources/localization/Midpoint.properties index d38316e8ed5..23cd61faf6f 100644 --- a/gui/admin-gui/src/main/resources/localization/Midpoint.properties +++ b/gui/admin-gui/src/main/resources/localization/Midpoint.properties @@ -840,14 +840,6 @@ OperationResultStatus.IN_PROGRESS=In progress OperationResultStatus.NOT_APPLICABLE=Not applicable OperationResultStatus.PARTIAL_ERROR=Partial error OperationResultStatus.SUCCESS=Success -OperationResultStatusType.FATAL_ERROR=Fatal Error -OperationResultStatusType.HANDLED_ERROR=Handled Error -OperationResultStatusType.IN_PROGRESS=In Progress -OperationResultStatusType.NOT_APPLICABLE=Not Applicable -OperationResultStatusType.PARTIAL_ERROR=Partial Error -OperationResultStatusType.SUCCESS=Success -OperationResultStatusType.UNKNOWN=Unknown -OperationResultStatusType.WARNING=Warning OperationResultStatus.UNKNOWN=Unknown OperationResultStatus.WARNING=Warning operation.unlinkShadow=Unlink account (Model) From 52691e7c0777b4b59d739b730b5f123019b1d9e7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Ga=C5=A1par=C3=ADk?= Date: Fri, 3 Jun 2016 15:22:59 +0200 Subject: [PATCH 3/5] fixed one typo in properties changed reference to midPoint to system/Identity Manager, by context --- .../localization/Midpoint.properties | 86 +++++++++---------- 1 file changed, 43 insertions(+), 43 deletions(-) diff --git a/gui/admin-gui/src/main/resources/localization/Midpoint.properties b/gui/admin-gui/src/main/resources/localization/Midpoint.properties index 23cd61faf6f..be59c439945 100644 --- a/gui/admin-gui/src/main/resources/localization/Midpoint.properties +++ b/gui/admin-gui/src/main/resources/localization/Midpoint.properties @@ -116,12 +116,12 @@ CapabilityStep.activation.tooltip.attributeName=Name of the attribute that conta CapabilityStep.activation.tooltip.disableList=List of attribute values that represent the "disabled" state. If any of these values are present in the attribute then the object will be considered to be disabled. Typical values are "false", "disabled", "0" or empty value. CapabilityStep.activation.tooltip.enabled=True if this capability is active. False if it is disabled. Disabled capability acts in the same way as if it was not there. Capabilities can be disabled e.g. to work around connector bugs, to make resource read-only, etc. CapabilityStep.activation.tooltip.enableList=List of attribute values that represent the "enabled" state. If any of these values are present in the attribute then the object will be considered to be enabled. Typical values are "true", "ENABLED", "1" and so on. -CapabilityStep.activation.tooltip.ignoreAttribute=If set to true then the attribute which is used for simulated activation will be mark as ignored in the schema. I.e. midPoint will pretend that this attribute does not exist and only use the standard administrativeStatus. This is the default. If set to false then the attribute will also be visible in the schema and both the administrativeStatus and the original attribute will work. This may be needed if the attribute has a richer set of states than the administrativeStatus attribute. But in this case beware of value conflicts between administrativeStatus and the original attribute. +CapabilityStep.activation.tooltip.ignoreAttribute=If set to true then the attribute which is used for simulated activation will be mark as ignored in the schema. I.e. system will pretend that this attribute does not exist and only use the standard administrativeStatus. This is the default. If set to false then the attribute will also be visible in the schema and both the administrativeStatus and the original attribute will work. This may be needed if the attribute has a richer set of states than the administrativeStatus attribute. But in this case beware of value conflicts between administrativeStatus and the original attribute. CapabilityStep.activation.tooltip.returnedByDefault=If true then the activation attribute is returned with resource objects by default and it does not need to be requested. If false then the activation attribute has to be explicitly requested. CapabilityStep.activation.tooltip.validFromEnabled=True if the resource supports validFrom activation property. CapabilityStep.activation.tooltip.validFromReturned=True of the validFrom property is returned by default. False if it needs to be explicitly requested. CapabilityStep.activation.tooltip.validToEnabled=True if the resource supports validTo activation property -CapabilityStep.activation.tooltip.validToReturned=True of the validFrom property is returned by default. False if it needs to be explicitly requested. +CapabilityStep.activation.tooltip.validToReturned=True of the validTo property is returned by default. False if it needs to be explicitly requested. CapabilityStep.capability.activation.tooltip=Activation capability. Ability to enable/disable accounts, set validity dates, etc. CapabilityStep.capability.create.tooltip=Capability to create (add) new objects on resource. CapabilityStep.capability.credentials.tooltip=Capability to set credentials for resource accounts. @@ -138,7 +138,7 @@ CapabilityStep.credentials.tooltip.passReturned=True of the password is returned CapabilityStep.message.cantLoadCaps=Couldn't load capabilities CapabilityStep.native=Native CapabilityStep.script.tooltip.enabled=True if this capability is active. False if it is disabled. Disabled capability acts in the same way as if it was not there. Capabilities can be disabled e.g. to work around connector bugs, to make resource read-only, etc. -CapabilityStep.script.tooltip.onConnector=Capability to execute scripts "on connector". This means that the scripts will be executed on the machine where the connector is installed. This is usually midPoint node or a connector server. +CapabilityStep.script.tooltip.onConnector=Capability to execute scripts "on connector". This means that the scripts will be executed on the machine where the connector is installed. This is usually system node or a connector server. CapabilityStep.script.tooltip.onResource=Capability to execute scripts "on resource". This means that the scripts will be executed on the machine where the connector connects. This is usually the server that hosts the resource (AD server, remote Unix machine, database server, etc.) CapabilityStep.title=Capabilities capabilityValuePanel.label.capability.create=Create capability @@ -704,8 +704,8 @@ operation.com.evolveum.midpoint.task.quartzimpl.execution.LocalNodeManager.stopS operation.com.evolveum.midpoint.task.quartzimpl.execution.RemoteNodesManager.addNodeStatusFromRemoteNode=Get status of remote node (Task) operation.com.evolveum.midpoint.task.quartzimpl.execution.RemoteNodesManager.stopRemoteScheduler=Stop remote scheduler (Task) operation.com.evolveum.midpoint.task.quartzimpl.execution.RemoteNodesManager.stopRemoteTaskRun=Stop remote task run (Task) -operation.com.evolveum.midpoint.task.quartzimpl.execution.TaskSynchronizer.synchronizeJobStores=Synchronize midPoint repository and Quartz Job Store (Task) -operation.com.evolveum.midpoint.task.quartzimpl.execution.TaskSynchronizer.synchronizeTask=Synchronize task in midPoint repository and Quartz Job Store (Task) +operation.com.evolveum.midpoint.task.quartzimpl.execution.TaskSynchronizer.synchronizeJobStores=Synchronize system repository and Quartz Job Store (Task) +operation.com.evolveum.midpoint.task.quartzimpl.execution.TaskSynchronizer.synchronizeTask=Synchronize task in system repository and Quartz Job Store (Task) operation.com.evolveum.midpoint.task.quartzimpl.GlobalExecutionManager.addNodeAndTaskInformation=Add node and task information (Task) operation.com.evolveum.midpoint.task.quartzimpl.GlobalExecutionManager.stopSchedulersAndTasks=Stop schedulers and tasks (Task) operation.com.evolveum.midpoint.task.quartzimpl.LocalExecutionManager.getLocallyRunningTasks=Get locally running tasks (Task) @@ -878,7 +878,7 @@ PageAbout.repoDiag.implementationDescription=Implementation description PageAbout.repoDiag.implementationShortName=Implementation name PageAbout.repoDiag.isEmbedded=Is embedded PageAbout.repoDiag.repositoryUrl=Repository URL -PageAbout.title=About midPoint +PageAbout.title=About this system PageAbout.title.basic=Basic PageAbout.title.jvmProperties=JVM properties PageAbout.title.provisioning=Provisioning @@ -1529,7 +1529,7 @@ PageLogin.signIn=Sign in PageLogin.title=Login PageLogin.username=Username PageMyPasswordQuestions.title=My Password Questions -PageMyPasswords.accountMidpoint=MidPoint +PageMyPasswords.accountMidpoint=Identity Manager PageMyPasswords.accounts=Accounts PageMyPasswords.button.back=Back PageMyPasswords.button.save=Save @@ -1539,7 +1539,7 @@ PageMyPasswords.importantNote=If selected, user password and all accounts' crede PageMyPasswords.name=Name PageMyPasswords.noAccountSelected=Password not changed. No account was selected. PageMyPasswords.password=Password -PageMyPasswords.resourceMidpoint=MidPoint Repository +PageMyPasswords.resourceMidpoint=Identity Repository PageMyPasswords.resourceName=Resource PageMyPasswords.title=My passwords PageNewReport.button.import=Import report @@ -1602,8 +1602,8 @@ PageReports.report.auditDescription=Report made from audit records. PageReports.report.auditName=Audit logs PageReports.report.reconciliationDescription=Reconciliation report for selected resource. PageReports.report.reconciliationName=Reconciliation -PageReports.report.usersDescription=Users listed in MidPoint. -PageReports.report.usersName=Users in MidPoint +PageReports.report.usersDescription=Users listed in Identity Manager. +PageReports.report.usersName=Users in Identity Manager PageReports.search.showSubreports=Show subreports PageReports.table.description=Description PageReports.table.name=Name @@ -2157,7 +2157,7 @@ processInstancePanel.name=Process instance name\: processInstancePanel.pid=Instance ID\: processInstancePanel.started=Started\: processInstancePanel.taskAlreadyRemoved=(was already removed) -processInstancePanel.task=MidPoint task\: +processInstancePanel.task=System task\: processInstancePanel.tasks=Currently active work items\: processInstancePanel.title.edit=Details for '{0}' ProfilingLevel.ARGUMENTS=Arguments @@ -2309,12 +2309,12 @@ ResourceWizard.expression.tooltip.expression=The XML representation of the expre ResourceWizard.expression.tooltip.language=Programming language in which is the expression script written. ResourceWizard.expression.tooltip.policyRef=Reference to a value policy object. The specified value policy will be used as a template to generate a value. ResourceWizard.expression.tooltip.type=The type of expression. This specifies whether the expression is a script, value generator or something else. -ResourceWizard.help.capabilityStep=

Resource capabilities are the things that the resource can do. Not all the resource are equal in their capabilities. E.g. one resource supports account activation (enabling and disabling accounts) but other does not. One resource provides read-write access while other can support read-only access. One resource supports real-time synchronization while other does not. The capabilities define what features the resource supports so midPoint can behave accordingly.

All the capabilities can be disabled (i.e. turned off). Disabling the capability will cause that midPoint will not use that part of the connector and resource. The capabilities are usually disabled if they are faulty. E.g. if there is a bug in a connector or on the resource then the bug might be circumvented if appropriate capability is disabled. But the capabilities may be disabled also for administrative reasons. E.g. disabling Create, Update and Delete capabilities makes the resource efficiently read-only.

Some capabilities can be simulated. It means that midPoint can pretend that the resource has specific capability even though it does not have it. E.g. an activation capability can be simulated by setting a specific account attribute to a specific value to disable an account. Such simulated capabilities usually require some configuration. This can also be configured on this page.

See https\://wiki.evolveum.com/display/midPoint/Resource+Capabilities wiki page for more details. +ResourceWizard.help.capabilityStep=

Resource capabilities are the things that the resource can do. Not all the resource are equal in their capabilities. E.g. one resource supports account activation (enabling and disabling accounts) but other does not. One resource provides read-write access while other can support read-only access. One resource supports real-time synchronization while other does not. The capabilities define what features the resource supports so system can behave accordingly.

All the capabilities can be disabled (i.e. turned off). Disabling the capability will cause that system will not use that part of the connector and resource. The capabilities are usually disabled if they are faulty. E.g. if there is a bug in a connector or on the resource then the bug might be circumvented if appropriate capability is disabled. But the capabilities may be disabled also for administrative reasons. E.g. disabling Create, Update and Delete capabilities makes the resource efficiently read-only.

Some capabilities can be simulated. It means that system can pretend that the resource has specific capability even though it does not have it. E.g. an activation capability can be simulated by setting a specific account attribute to a specific value to disable an account. Such simulated capabilities usually require some configuration. This can also be configured on this page.

See https\://wiki.evolveum.com/display/midPoint/Resource+Capabilities wiki page for more details. ResourceWizard.help.configurationStep=

This stage of the wizard configures connector configuration properties. They usually define network parameters used to access the resource such as hostname and port numbers. Additional connection parameters such as operation network timeouts and connection pooling configuration can be specified here.

There connector configuration properties are unique for each connector. The specific set of configuration properties are determined by connector configuration schema. Therefore the content of this page depends on the connector type that was selected in the previous page.

-ResourceWizard.help.nameStep=

This stage of the wizard configures basic properties of the resource. It can be used to configure resource name and description. Connector name is mandatory and must be unique. Connector that will be used to access the resource must also be configured. Connectors are deployed on connector hosts. If the connector host is left empty then connectors deployed directly in the midPoint instance will be used.

See Resource Configuration wiki page for detailed explanation of resource configuration.

-ResourceWizard.help.schemaHandlingStep=

This step is used to provide configuration for handling of resource schema. The configuration displayed on this page tells midPoint what to do with resource object classes and attributes. It contains the configuration of mappings between user properties and account attributes, configuration of account types, groups, provisioning dependencies, password mapping and so on.

The configuration is grouped into object types. Each object type defines the behavior for specific account type, entitlement type, OU, etc. The object type is uniquely identified by the combination of kind and intent. The kind defines what kind of the object it is\:

  • kind\=account means that the object is an account, i.e. that it represents a user.
  • kind\=entitlement is applied to groups, roles, privileges, ACIs and similar objects that can be associated with accounts and which give privileges or access rights to the account.
  • kind\=generic applies to other objects such as organizational units (OUs), domains, etc.
Intent is a plain string that can be used to distinguish several object types. E.g. it can be used to define several account type, e.g. "default user account", "administration account", "testing account" and so on. See Kind, Intent and ObjectClass wiki page for more details.

More details about schema handling configuration are provided on Resource Schema Handling wiki page. -ResourceWizard.help.schemaStep=

This page shows resource schema. The resource schema defines object classes that the connector can manage, e.g. accounts, groups, organizational units and so on. The schema defines a set of attributes for each object class. The schema is presented here in read-only form so you can inspect it and familiarize yourself with the data model that the resource provides.

The resource schema presented at this page is usually retrieved from the resource and automatically generated by midPoint. Resource schema defines what the resource can do, i.e. what object classes it defines and what attributes are used in the object classes. Therefore the schema is read-only. It is not a configuration. It does not defines how midPoint uses the object classes and attributes. That is configured in next steps of the wizard.

See Resource Schema wiki page for detailed explanation of resource schema concepts

-ResourceWizard.help.synchronizationStep=

The synchronization configuration defines how midPoint reacts when it discovers that resource object has changed. E.g. it defines how midPoint reacts when it discovers new account, when it discovers that a group that should exist does not and so on. It is usually does not matter how midPoint discovers the change the reaction is usually the same (although exceptions are possible by using channel specification). Therefore the policy that is configured here usually applies to live synchronization, reconciliation, import, discovery (consistency mechanism) and possible also other mechanisms that may come in the future.

See Synchronization Configuration wiki page for more details. +ResourceWizard.help.nameStep=

This stage of the wizard configures basic properties of the resource. It can be used to configure resource name and description. Connector name is mandatory and must be unique. Connector that will be used to access the resource must also be configured. Connectors are deployed on connector hosts. If the connector host is left empty then connectors deployed directly in the system instance will be used.

See Resource Configuration wiki page for detailed explanation of resource configuration.

+ResourceWizard.help.schemaHandlingStep=

This step is used to provide configuration for handling of resource schema. The configuration displayed on this page tells system what to do with resource object classes and attributes. It contains the configuration of mappings between user properties and account attributes, configuration of account types, groups, provisioning dependencies, password mapping and so on.

The configuration is grouped into object types. Each object type defines the behavior for specific account type, entitlement type, OU, etc. The object type is uniquely identified by the combination of kind and intent. The kind defines what kind of the object it is\:

  • kind\=account means that the object is an account, i.e. that it represents a user.
  • kind\=entitlement is applied to groups, roles, privileges, ACIs and similar objects that can be associated with accounts and which give privileges or access rights to the account.
  • kind\=generic applies to other objects such as organizational units (OUs), domains, etc.
Intent is a plain string that can be used to distinguish several object types. E.g. it can be used to define several account type, e.g. "default user account", "administration account", "testing account" and so on. See Kind, Intent and ObjectClass wiki page for more details.

More details about schema handling configuration are provided on Resource Schema Handling wiki page. +ResourceWizard.help.schemaStep=

This page shows resource schema. The resource schema defines object classes that the connector can manage, e.g. accounts, groups, organizational units and so on. The schema defines a set of attributes for each object class. The schema is presented here in read-only form so you can inspect it and familiarize yourself with the data model that the resource provides.

The resource schema presented at this page is usually retrieved from the resource and automatically generated by system. Resource schema defines what the resource can do, i.e. what object classes it defines and what attributes are used in the object classes. Therefore the schema is read-only. It is not a configuration. It does not defines how system uses the object classes and attributes. That is configured in next steps of the wizard.

See Resource Schema wiki page for detailed explanation of resource schema concepts

+ResourceWizard.help.synchronizationStep=

The synchronization configuration defines how Identity Manager reacts when it discovers that resource object has changed. E.g. it defines how system reacts when it discovers new account, when it discovers that a group that should exist does not and so on. It is usually does not matter how system discovers the change the reaction is usually the same (although exceptions are possible by using channel specification). Therefore the policy that is configured here usually applies to live synchronization, reconciliation, import, discovery (consistency mechanism) and possible also other mechanisms that may come in the future.

See Synchronization Configuration wiki page for more details. runReportPopupContent.button.run=Run report runReportPopupContent.param.class=Parameter type runReportPopupContent.param.name.eventStage = Event Stage @@ -2341,15 +2341,15 @@ RunReportPopupPanel.title=Report configuration before run runUntilNodeDown.error1=Compatible data for 'Thread stop action' are\: Close, Suspend runUntilNodeDown.error2=Compatible data for 'Thread stop action' are\: Restart, Reschedule SchemaHandlingStep.activation.tooltip.fetchStrategy=How to fetch the attribute when it is needed. Implicit\: the attribute is returned by default, it does not need to be requested; Explicit\: the attribute is not returned by default, always request it explicitly. -SchemaHandlingStep.activation.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the midPoint (usually a user). -SchemaHandlingStep.activation.tooltip.outbound=Outbound mappings map values from midPoint (usually a user) to the resource (usually an account). +SchemaHandlingStep.activation.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the Identity Manager (usually a user). +SchemaHandlingStep.activation.tooltip.outbound=Outbound mappings map values from Identity Manager (usually a user) to the resource (usually an account). SchemaHandlingStep.association.label.associationName=Association name SchemaHandlingStep.association.label.associationNamespace=Association namespace SchemaHandlingStep.association.tooltip.associationAttribute=Name of the attribute that "holds" the association. I.e. an attribute which contains the identifier of the associated object. This is usually an attribute such as "memeber", "groups", "roles", etc. In subject-to-object associations this is an attribute of a subject (e.g. account attribute "groups"). In object-to-subject associations this is an attribute of an object (e.g. group attribute "members"). SchemaHandlingStep.association.tooltip.associationLocalPart=TODO\: SchemaHandlingStep.association.tooltip.associationLocalPart SchemaHandlingStep.association.tooltip.associationNamespace=TODO\: SchemaHandlingStep.association.tooltip.associationNamespace SchemaHandlingStep.association.tooltip.direction=Defines the direction of the association. Object-to-subject\: Object (e.g. group) has an attribute that contains identifier of the subject (e.g. account); Subject-to-object\: Subject (e.g. account) has an attribute that contains identifier of the object (e.g. group). -SchemaHandlingStep.association.tooltip.explicitRefIntegrity=Explicit referential integrity. If set to false then midPoint assumes that the resource implements referential integrity. E.g. midPoint assumes that the resource automatically updates the association identifiers if an account is renamed and midPoint does not need to do anything. If set to true then midPoint will do referential integrity explicitly. In this case midPoint will explicitly update the association attributes if an account is renamed. +SchemaHandlingStep.association.tooltip.explicitRefIntegrity=Explicit referential integrity. If set to false then system assumes that the resource implements referential integrity. E.g. system assumes that the resource automatically updates the association identifiers if an account is renamed and system does not need to do anything. If set to true then system will do referential integrity explicitly. In this case system will explicitly update the association attributes if an account is renamed. SchemaHandlingStep.association.tooltip.intent=Intent of the association target object type. Target kind and intent identify an object type which is association target, e.g. a group, privilege, role, etc. SchemaHandlingStep.association.tooltip.kind=Kind of the association target object type. This is usually "entitlement". Target kind and intent identify an object type which is association target, e.g. a group, privilege, role, etc. SchemaHandlingStep.association.tooltip.valueAttribute=Name of the attribute that is the source of a value for the association. The value of this attribute will be taken and stored into the association attribute to form an association. This is usually an attribute that contains an identifier or name such as "uid", "id", "name", etc. In subject-to-object associations this is an attribute of an object (e.g. group). In object-to-subject associations this is an attribute of a subject (e.g. account). @@ -2360,18 +2360,18 @@ SchemaHandlingStep.attribute.tooltip.attributeLocalPart=TODO\: SchemaHandlingSte SchemaHandlingStep.attribute.tooltip.attributeNamespace=TODO\: SchemaHandlingStep.attribute.tooltip.attributeNamespace SchemaHandlingStep.attribute.tooltip.exclusiveStrong=When set to false then both strong and normal mapping values are merged to produce the final set of values. When set to true only strong values are used if there is at least one strong mapping. Normal values are used if there is no strong mapping. SchemaHandlingStep.attribute.tooltip.fetchStrategy=How to fetch the attribute when it is needed. Implicit\: the attribute is returned by default, it does not need to be requested; Explicit\: the attribute is not returned by default, always request it explicitly. -SchemaHandlingStep.attribute.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the midPoint (usually a user). -SchemaHandlingStep.attribute.tooltip.intolerantVP=A value that matches this pattern will NOT be tolerated. I.e. it will be erased from the attribute value even if it is not a result of midPoint processing (mappings). +SchemaHandlingStep.attribute.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the system (usually a user). +SchemaHandlingStep.attribute.tooltip.intolerantVP=A value that matches this pattern will NOT be tolerated. I.e. it will be erased from the attribute value even if it is not a result of system processing (mappings). SchemaHandlingStep.attribute.tooltip.limitations=Specify attribute limitations such as multiplicity, ability to read or write it, etc. SchemaHandlingStep.attribute.tooltip.matchingRule=A rule that determines if two attribute values have the same meaning. E.g. setting this to 'stringIgnoreCase' will make this attribute efficiently case insensitive. -SchemaHandlingStep.attribute.tooltip.outbound=Outbound mappings map values from midPoint (usually a user) to the resource (usually an account). +SchemaHandlingStep.attribute.tooltip.outbound=Outbound mappings map values from system (usually a user) to the resource (usually an account). SchemaHandlingStep.attribute.tooltip.reference=Name of the attribute to configure. All the settings and mappings below apply to this attribute. -SchemaHandlingStep.attribute.tooltip.tolerant=Tolerant attributes tolerate values that are set outside of midPoint. Non-tolerant attributes will only allow values that are defined in midPoint (e.g. by resource or role mappings). -SchemaHandlingStep.attribute.tooltip.tolerantVP=A value that matches this pattern will be tolerated. I.e. it will remain as the attribute value even if it is not a result of midPoint processing (mappings). +SchemaHandlingStep.attribute.tooltip.tolerant=Tolerant attributes tolerate values that are set outside of system. Non-tolerant attributes will only allow values that are defined in system (e.g. by resource or role mappings). +SchemaHandlingStep.attribute.tooltip.tolerantVP=A value that matches this pattern will be tolerated. I.e. it will remain as the attribute value even if it is not a result of system processing (mappings). SchemaHandlingStep.button.add=Add object type SchemaHandlingStep.credentials.tooltip.fetchStrategy=How to fetch the credentials value when it is needed. Implicit\: the value is returned by default, it does not need to be requested; Explicit\: the value is not returned by default, always request it explicitly. -SchemaHandlingStep.credentials.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the midPoint (usually a user). -SchemaHandlingStep.credentials.tooltip.outbound=Outbound mappings map values from midPoint (usually a user) to the resource (usually an account). +SchemaHandlingStep.credentials.tooltip.inbound=Inbound mappings map values from the resource (usually an account) to the system (usually a user). +SchemaHandlingStep.credentials.tooltip.outbound=Outbound mappings map values from system (usually a user) to the resource (usually an account). SchemaHandlingStep.credentials.tooltip.passwordPolicyRef=Password policy to apply to this credential. This setting overrides other settings, e.g. default password policy defined in system configuration. If no password policy is defined here then the usual default will be used. SchemaHandlingStep.dependency.tooltip.intent=Intent of the object on which we depend. SchemaHandlingStep.dependency.tooltip.kind=Kind of the object on which we depend. @@ -2397,7 +2397,7 @@ SchemaHandlingStep.label.newObjectType=New object type SchemaHandlingStep.label.objectClass=Object class SchemaHandlingStep.label.objectTypes=Object types SchemaHandlingStep.label.protected=Protected -SchemaHandlingStep.limitations.tooltip.ignore=Flag to ignore an attribute. MidPoint will pretend that the ignored attribute does not exist at all. It will not display it in the user interface, will not apply mappings, etc. +SchemaHandlingStep.limitations.tooltip.ignore=Flag to ignore an attribute. System will pretend that the ignored attribute does not exist at all. It will not display it in the user interface, will not apply mappings, etc. SchemaHandlingStep.limitations.tooltip.layers=System layers to which this limitation applies. Sometimes the limitation does not apply equally to all the layers. E.g. the attribute may be formally read-write but we want it to be only presented as read-only by the user interface and change it only through mappings. In such a case the read-only limitation applies only to "presentation" layer. SchemaHandlingStep.limitations.tooltip.maxOccurs=Maximum number of occurrences of the attribute. A of one means single-value attribute, value of "unbounded" means multi-value attribute. A value which is specified here overrides the value taken from resource schema. SchemaHandlingStep.limitations.tooltip.minOccurs=Minimum number of occurrences of the attribute. A value of zero means optional attribute, value of one means mandatory attribute. A value which is specified here overrides the value taken from resource schema. @@ -2435,11 +2435,11 @@ SchemaHandlingStep.tooltip.credentials=Definition how to handle credentials such SchemaHandlingStep.tooltip.default=If set to true then this definition is the default for its kind. I.e. if no intent is explicitly specified then this definition will be used. SchemaHandlingStep.tooltip.dependency=Dependencies are object types that has to be processed before this object types is processed. I.e. this object type depends on them. The object types on which this object type depends will be provisioned before this object type. Dependencies are used to impose ordering into provisioning operations. SchemaHandlingStep.tooltip.filterClause=TODO\: SchemaHandlingStep.tooltip.filterClause -SchemaHandlingStep.tooltip.intent=Intent specifies what midPoint should do with the object. Intent sorts objects of the same kind into several categories. Objects with different intents may be handled differently by midPoint. -SchemaHandlingStep.tooltip.iteration=Iteratively find values for unique attributes such as identifiers. MidPoint will try several times to find a unique value for such attributes. +SchemaHandlingStep.tooltip.intent=Intent specifies what system should do with the object. Intent sorts objects of the same kind into several categories. Objects with different intents may be handled differently by system. +SchemaHandlingStep.tooltip.iteration=Iteratively find values for unique attributes such as identifiers. Identity Manager will try several times to find a unique value for such attributes. SchemaHandlingStep.tooltip.kind=Kind specified what this object is, whether it is account, entitlement or something else. SchemaHandlingStep.tooltip.objectClass=Object class from the schema that will be used to construct instances of this object type. -SchemaHandlingStep.tooltip.protected=Specification of protected instances of this object type. MidPoint can see protected instances but they cannot be touched. Any attempt to modify them will fail. This is used to protect emergency administration accounts such as "root" or "administrator". +SchemaHandlingStep.tooltip.protected=Specification of protected instances of this object type. System can see protected instances but they cannot be touched. Any attempt to modify them will fail. This is used to protect emergency administration accounts such as "root" or "administrator". SchemaHandlingStep.duplicateObjectTypeWarning=There are more definitions for kind/intent: {0}. SchemaHandlingStep.in=in: {0} SchemaHandlingStep.out=out @@ -2465,7 +2465,7 @@ SchemaStep.message.reload.fail=Schema for resource '{0}' was not reloaded. SchemaStep.message.reload.ok=Schema for resource '{0}' was reloaded successfully. SchemaStep.schema=Schema SchemaStep.title=Schema -SchemaStep.tooltip.intent=Intent specifies what midPoint should do with the object. Intent sorts objects of the same kind into several categories. Objects with different intents may be handled differently by midPoint. +SchemaStep.tooltip.intent=Intent specifies what system should do with the object. Intent sorts objects of the same kind into several categories. Objects with different intents may be handled differently by system. SchemaStep.tooltip.isDefault=If set to true then this definition is the default for its kind. I.e. if no intent is explicitly specified then this definition will be used. SchemaStep.tooltip.kind=Kind specified what this object is, whether it is account, entitlement or something else. SchemaStep.tooltip.nativeObjectClass=Object class name how it is natively known by the resource (or the connector). @@ -2549,8 +2549,8 @@ SynchronizationReactionEditor.label.objectTemplateRef=Object template ref. SynchronizationReactionEditor.label.reconcile=Reconcile SynchronizationReactionEditor.label.situation=Situation SynchronizationReactionEditor.label.synchronize=Synchronize -SynchronizationStep.action.tooltip.handlerUri=The explicit action to execute. Please note that most actions are designed to work with the default midPoint synchronization algorithm and that this algorithm will be executed unless it was explicitly disabled (and then the result may be an error). Also note that even if no explicit action is selected midPoint will still do the default synchronization algorithm is the "synchronize" option was selected. -SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before midPoint default synchronization algorithms or after them. Most built-in actions are designed to be executed before midPoint synchronization as they only set up the model context and then they ley midPoint to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. +SynchronizationStep.action.tooltip.handlerUri=The explicit action to execute. Please note that most actions are designed to work with the default Identity Manager's synchronization algorithm and that this algorithm will be executed unless it was explicitly disabled (and then the result may be an error). Also note that even if no explicit action is selected system will still do the default synchronization algorithm is the "synchronize" option was selected. +SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before Identity Manager's default synchronization algorithms or after them. Most built-in actions are designed to be executed before system synchronization as they only set up the model context and then they ley system to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. SynchronizationStep.button.add=Add synchronization object SynchronizationStep.label.condition=Condition SynchronizationStep.label.confirmation=Confirmation @@ -2574,7 +2574,7 @@ SynchronizationStep.message.cantSave=Couldn't save resource synchronization. SynchronizationStep.message.errorLoadingObjectSyncList=Couldn't load object synchronization list from resource. Error\: SynchronizationStep.message.errorLoadingObjectTemplates=Couldn't load object templates from repository. SynchronizationStep.message.unsupportedActionFormat=You are using deprecated attribute 'ref' to define reaction action. Use element 'handlerUri' instead. Actions with 'ref' attribute will not be shown in this wizard. -SynchronizationStep.reaction.tooltip.action=Explicit action. This setting defines what midPoint has to do as a reaction to the synchronization event. +SynchronizationStep.reaction.tooltip.action=Explicit action. This setting defines what system has to do as a reaction to the synchronization event. SynchronizationStep.reaction.tooltip.channel=Channel limitation. If the synchronization event originated from the specified channel (e.g. live sync, reconciliation or import) then this reaction will be processed. It will be ignored otherwise. SynchronizationStep.reaction.tooltip.objectTemplateRef=Object template that will be used to process this specific synchronization event. If no object template is specified here then the usual default will be used. SynchronizationStep.reaction.tooltip.reconcile=If set to true then the reconciliation step will be forced for this synchronization event. The attributes will be explicitly fetched is they are not present. If set to false then the reconciliation will be automatic. In that case the reconciliation happens only if the attributes are already present in the synchronization event. If the attributes are not present they will not be explicitly fetched and the reconciliation will be skipped. @@ -2591,7 +2591,7 @@ SynchronizationStep.tooltip.kind=Object kind for which this definition applies. SynchronizationStep.tooltip.objectClass=Object class for which this definition applies. This will be used to select the synchronization settings in case the object (shadow) does not have kind/intent definition yet. SynchronizationStep.tooltip.objectTemplate=Object template that will be used to process this specific synchronization event. If no object template is specified here then the usual default will be used. SynchronizationStep.tooltip.opportunistic=If set to true then opportunistic synchronization (a.k.a. discovery) will be enabled during the processing of this event. -SynchronizationStep.tooltip.reaction=Specifies how midPoint reacts to this synchronization event. Several reactions can be specified. The reaction appropriate for the synchronization situation of the event will be selected. +SynchronizationStep.tooltip.reaction=Specifies how system reacts to this synchronization event. Several reactions can be specified. The reaction appropriate for the synchronization situation of the event will be selected. SynchronizationStep.tooltip.reconcile=If set to true then the reconciliation step will be forced for this synchronization event. The attributes will be explicitly fetched is they are not present. If set to false then the reconciliation will be automatic. In that case the reconciliation happens only if the attributes are already present in the synchronization event. If the attributes are not present they will not be explicitly fetched and the reconciliation will be skipped. SynchronizationStep.duplicateObjectTypeWarning=There are more synchronization definitions for kind/intent: {0}. SystemConfigPanel.assignmentPolicyEnforcement=Assignment policy enforcement @@ -2796,7 +2796,7 @@ WebModelUtils.couldntLoadObject=Couldn't load object. WebModelUtils.couldntSaveObject=Couldn't save object. WebModelUtils.couldntSearchObjects=Couldn't search objects. WebModelUtils.couldntDeleteObject=Couldn't delete object. -web.security.provider.access.denied=Access denied. You don't have permission to access, please contact midPoint's administrators. +web.security.provider.access.denied=Access denied. You don't have permission to access, please contact Identity Manager's administrators. web.security.provider.denied=Permission denied. web.security.provider.disabled=User is disabled. web.security.provider.invalid=Invalid username and/or password. @@ -2858,8 +2858,8 @@ PageSelfCredentials.title=Credentials PageSelfCredentials.oldPasswordLabel=Old password PageSelfCredentials.passwordLabel1=New password PageSelfCredentials.passwordLabel2=Confirm password -PageSelfCredentials.accountMidpoint=MidPoint -PageSelfCredentials.resourceMidpoint=MidPoint Repository +PageSelfCredentials.accountMidpoint=Identity Manager +PageSelfCredentials.resourceMidpoint=Identity Repository PageSelfCredentials.noAccountSelected=Password not changed. No account was selected. PageSelfCredentials.incorrectOldPassword=Password not changed. Old password is incorrect. PageSelfCredentials.specifyOldPasswordMessage=Please, specify old password value @@ -2870,7 +2870,7 @@ ChangePasswordPanel.enabled=Enabled ChangePasswordPanel.legendMessage.selected= - Password will be changed ChangePasswordPanel.legendMessage.propagated= - Automatic password propagation (based on policies defined in resources definitions) ChangePasswordPanel.legendMessage.deselected= - Password will not be changed -ChangePasswordPanel.helpInfo=

This portion of the credentials dialog controls how the password change will be propagated to each individual system. The first line defines whether the password will be changed in the midPoint itself. Following lines represent each system for which the password can be changed. The password propagation is controlled by the icons:

  • Password will be changed. Password for this system will be changed to the value specified in the password dialog above.
  • Automatic password propagation. The password might be changed. Whether the password is changed or not depends on the policies set up by identity administrator. This usually means that the password will be changed if it makes sense for the current situation and settings. This is the reasonable default choice.
  • Password will not be changed for this system.

You can adjust the password propagation settings by clicking on the icons and thus fine-tune how the password change is propagated to each individual system.

+ChangePasswordPanel.helpInfo=

This portion of the credentials dialog controls how the password change will be propagated to each individual system. The first line defines whether the password will be changed in the Identity Manager itself. Following lines represent each system for which the password can be changed. The password propagation is controlled by the icons:

  • Password will be changed. Password for this system will be changed to the value specified in the password dialog above.
  • Automatic password propagation. The password might be changed. Whether the password is changed or not depends on the policies set up by identity administrator. This usually means that the password will be changed if it makes sense for the current situation and settings. This is the reasonable default choice.
  • Password will not be changed for this system.

You can adjust the password propagation settings by clicking on the icons and thus fine-tune how the password change is propagated to each individual system.

ChangePasswordPanel.helpPopupTitle=Password propagation help PageBase.button.tooltip.clearSearch=Clear mainForm.uploadTooLarge = Upload must be less than ${maxSize}. @@ -3018,8 +3018,8 @@ TreeTablePanel.menu.recomputeMembersSelected=Recompute selected members TreeTablePanel.menu.recomputeMembersAll=Recompute all members TreeTablePanel.menu.recomputeManagersAll=Recompute all managers TreeTablePanel.menu.deleteManagersAll=Delete all managers -TreeTablePanel.menu.deleteManager.confirm=Are you sure you want to delete selected manager from midPoint? This change is permanent. -TreeTablePanel.menu.deleteManagersAll.confirm=All defined managers will be permanently removed from midPoint. Are you sure to perform this action? +TreeTablePanel.menu.deleteManager.confirm=Are you sure you want to delete selected manager from system? This change is permanent. +TreeTablePanel.menu.deleteManagersAll.confirm=All defined managers will be permanently removed from system. Are you sure to perform this action? TreeTablePanel.move=Move TreeTablePanel.makeRoot=Make root TreeTablePanel.delete=Delete @@ -3119,5 +3119,5 @@ operation.com.evolveum.midpoint.web.page.admin.configuration.PageSystemConfigura peration.com.evolveum.midpoint.web.page.admin.server.PageTaskEdit.saveTask=Save task (GUI) operation.com.evolveum.midpoint.notifications.impl.notifiers.GeneralNotifier.processEvent=Process event (Notification) operation.com.evolveum.midpoint.model.impl.lens.ChangeExecutor.execute.focus.OrgType=Execute OrgType (Model) -TreeTablePanel.menu.deleteMember.confirm=All selected members (users, organizations, services, roles) will be permanently deleted from midPoint. Are you sure to perform this action? -TreeTablePanel.menu.deleteAllMembers.confirm=All focus members (users, organizations, services, roles) will be permanently deleted from midPoint. Are you sure to perform this action? +TreeTablePanel.menu.deleteMember.confirm=All selected members (users, organizations, services, roles) will be permanently deleted from system. Are you sure to perform this action? +TreeTablePanel.menu.deleteAllMembers.confirm=All focus members (users, organizations, services, roles) will be permanently deleted from system. Are you sure to perform this action? From 3877e402f0807741f22519d7dfad692679d3a855 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Ga=C5=A1par=C3=ADk?= Date: Fri, 3 Jun 2016 15:44:34 +0200 Subject: [PATCH 4/5] more typos, thanks to AivoK, who spotted them --- .../src/main/resources/localization/Midpoint.properties | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gui/admin-gui/src/main/resources/localization/Midpoint.properties b/gui/admin-gui/src/main/resources/localization/Midpoint.properties index be59c439945..e559f3d360d 100644 --- a/gui/admin-gui/src/main/resources/localization/Midpoint.properties +++ b/gui/admin-gui/src/main/resources/localization/Midpoint.properties @@ -1560,7 +1560,7 @@ PageOrgUnit.title.approvers=Approvers PageOrgUnit.title.assignments=Assignments PageOrgUnit.title.authorizations=Authorizations PageOrgUnit.title.basic=Basic -PageOrgUnit.title.exclusions=Exclutions +PageOrgUnit.title.exclusions=Exclusions PageOrgUnit.title.inducements=Inducements PageOrgUnit.title=New org. unit PageOrgUnit.title.parentOrgUnit=Parent(s) @@ -2550,7 +2550,7 @@ SynchronizationReactionEditor.label.reconcile=Reconcile SynchronizationReactionEditor.label.situation=Situation SynchronizationReactionEditor.label.synchronize=Synchronize SynchronizationStep.action.tooltip.handlerUri=The explicit action to execute. Please note that most actions are designed to work with the default Identity Manager's synchronization algorithm and that this algorithm will be executed unless it was explicitly disabled (and then the result may be an error). Also note that even if no explicit action is selected system will still do the default synchronization algorithm is the "synchronize" option was selected. -SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before Identity Manager's default synchronization algorithms or after them. Most built-in actions are designed to be executed before system synchronization as they only set up the model context and then they ley system to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. +SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before Identity Manager's default synchronization algorithms or after them. Most built-in actions are designed to be executed before system synchronization as they only set up the model context and then they let system to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. SynchronizationStep.button.add=Add synchronization object SynchronizationStep.label.condition=Condition SynchronizationStep.label.confirmation=Confirmation @@ -3069,7 +3069,7 @@ StageDefinitionPanel.reviewerUseObjectManagerOrgTypeHelp=Influences determinatio select only organizations with given organization type value - for example, 'functional' (if you have e.g. both functional-type and project-type organizations). \ If this field is empty, we take into account all organizations. If we find no suitable manager, we continue with all \ parent organizations (again, of the given type, if specified). -StageDefinitionPanel.reviewerUseObjectManagerAllowSelfHelp=If a user is a manager in his organization, could he be selected as an reviewer for his own assignments? If unchecked (the default), \ +StageDefinitionPanel.reviewerUseObjectManagerAllowSelfHelp=If a user is a manager in his organization, could he be selected as a reviewer for his own assignments? If unchecked (the default), \ a higher-level manager is searched for - see description for the above field. StageDefinitionPanel.defaultReviewerRefHelp=This reviewer (or reviewers) will be used if the above condition would lead to no reviewer. StageDefinitionPanel.additionalReviewerRefHelp=This reviewer (or reviewers) will be used in addition to any reviewers selected by the above conditions. From 17b80f0faf34292db417aecb68c44a9fc09fb14b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Ga=C5=A1par=C3=ADk?= Date: Fri, 3 Jun 2016 15:44:34 +0200 Subject: [PATCH 5/5] more typos, thanks to AivoK, who spotted them --- .../src/main/resources/localization/Midpoint.properties | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gui/admin-gui/src/main/resources/localization/Midpoint.properties b/gui/admin-gui/src/main/resources/localization/Midpoint.properties index be59c439945..2571cc59969 100644 --- a/gui/admin-gui/src/main/resources/localization/Midpoint.properties +++ b/gui/admin-gui/src/main/resources/localization/Midpoint.properties @@ -642,7 +642,7 @@ operation.com.evolveum.midpoint.model.synchronizer.ReconciliationProcessor.proce operation.com.evolveum.midpoint.model.synchronizer.UserSynchronizer.checkAccountContextReconciliation=Check account context reconciliation (Model) operation.com.evolveum.midpoint.model.sync.SynchronizeAccountResultHandler.handle=Synchronize account result handler, handle (Model) operation.com.evolveum.midpoint.notifications.AccountOperationListener.notifyFailure=Notify failure (Notifications) -operation.com.evolveum.midpoint.notifications.AccountOperationListener.notifyInProgress=Nofify in progress (Notifications) +operation.com.evolveum.midpoint.notifications.AccountOperationListener.notifyInProgress=Notify in progress (Notifications) operation.com.evolveum.midpoint.notifications.AccountOperationListener.notifySuccess=Notify success (Notifications) operation.com.evolveum.midpoint.provisioning.api.ProvisioningService.addObject=Add object (Provisioning) operation.com.evolveum.midpoint.provisioning.api.ProvisioningService.deleteObject=Delete object (Provisioning) @@ -1560,7 +1560,7 @@ PageOrgUnit.title.approvers=Approvers PageOrgUnit.title.assignments=Assignments PageOrgUnit.title.authorizations=Authorizations PageOrgUnit.title.basic=Basic -PageOrgUnit.title.exclusions=Exclutions +PageOrgUnit.title.exclusions=Exclusions PageOrgUnit.title.inducements=Inducements PageOrgUnit.title=New org. unit PageOrgUnit.title.parentOrgUnit=Parent(s) @@ -2550,7 +2550,7 @@ SynchronizationReactionEditor.label.reconcile=Reconcile SynchronizationReactionEditor.label.situation=Situation SynchronizationReactionEditor.label.synchronize=Synchronize SynchronizationStep.action.tooltip.handlerUri=The explicit action to execute. Please note that most actions are designed to work with the default Identity Manager's synchronization algorithm and that this algorithm will be executed unless it was explicitly disabled (and then the result may be an error). Also note that even if no explicit action is selected system will still do the default synchronization algorithm is the "synchronize" option was selected. -SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before Identity Manager's default synchronization algorithms or after them. Most built-in actions are designed to be executed before system synchronization as they only set up the model context and then they ley system to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. +SynchronizationStep.action.tooltip.order=Whether the explicit action is executed before Identity Manager's default synchronization algorithms or after them. Most built-in actions are designed to be executed before system synchronization as they only set up the model context and then they let system to do the real work. However some custom action may need to be executed after the synchronization, e.g. to deliver notifications, clean up, etc. SynchronizationStep.button.add=Add synchronization object SynchronizationStep.label.condition=Condition SynchronizationStep.label.confirmation=Confirmation @@ -3069,7 +3069,7 @@ StageDefinitionPanel.reviewerUseObjectManagerOrgTypeHelp=Influences determinatio select only organizations with given organization type value - for example, 'functional' (if you have e.g. both functional-type and project-type organizations). \ If this field is empty, we take into account all organizations. If we find no suitable manager, we continue with all \ parent organizations (again, of the given type, if specified). -StageDefinitionPanel.reviewerUseObjectManagerAllowSelfHelp=If a user is a manager in his organization, could he be selected as an reviewer for his own assignments? If unchecked (the default), \ +StageDefinitionPanel.reviewerUseObjectManagerAllowSelfHelp=If a user is a manager in his organization, could he be selected as a reviewer for his own assignments? If unchecked (the default), \ a higher-level manager is searched for - see description for the above field. StageDefinitionPanel.defaultReviewerRefHelp=This reviewer (or reviewers) will be used if the above condition would lead to no reviewer. StageDefinitionPanel.additionalReviewerRefHelp=This reviewer (or reviewers) will be used in addition to any reviewers selected by the above conditions.