Commit 1ced68b7 authored by Romain Bioteau's avatar Romain Bioteau
Browse files

Merge pull request #276 from bonitasoft/fix/uiDesignerWithCapitalLetter

BS-14301: use capital letter for the D of UI Designer
parents 5240aaba 72c6fd53
contractSectionDescription=Define a contract for this step or pool instantiation.
processContractSectionDescription=A contract defines the information that a process requires for instantiation.\nAfter you have defined the contract, you can generate the form by clicking the UI designer icon on the right of this panel. This generates a form with the relevant widgets and data bindings for the process instantiation inputs. You must handle constraints with validation in the form.\nYou can use contract input values as the initial value of variables, documents and search keys or in connectors in (on enter).
stepContractSectionDescription=A contract defines the information that a task requires to execute. If inputs are missing or constraints are not fulfilled on form submission, the task is not executed and stays ready.\nAfter you have defined the contract, you can generate the form by clicking the UI designer icon on the right of this panel. This generates a form with the relevant widgets and data bindings for the task inputs. You must handle constraints with validation in the form.\nYou can use a contract input value in operations and connectors out (on finish).
processContractSectionDescription=A contract defines the information that a process requires for instantiation.\nAfter you have defined the contract, you can generate the form by clicking the UI Designer icon on the right of this panel. This generates a form with the relevant widgets and data bindings for the process instantiation inputs. You must handle constraints with validation in the form.\nYou can use contract input values as the initial value of variables, documents and search keys or in connectors in (on enter).
stepContractSectionDescription=A contract defines the information that a task requires to execute. If inputs are missing or constraints are not fulfilled on form submission, the task is not executed and stays ready.\nAfter you have defined the contract, you can generate the form by clicking the UI Designer icon on the right of this panel. This generates a form with the relevant widgets and data bindings for the task inputs. You must handle constraints with validation in the form.\nYou can use a contract input value in operations and connectors out (on finish).
name=Name
type=Type
mandatory=Mandatory
......
......@@ -13,14 +13,14 @@ caseOverviewFormMappingDescription=The overview page is displayed in Bonita BPM
newFormTooltipForPool=Create or edit a form based on the contract. It will be automatically mapped to this pool.
newFormTooltipForTask=Create or edit a form based on the contract. It will be automatically mapped to this task.
legacyForm=6.x
openUIDesigner=Open UI designer
uiDesignerLabel=UI designer
openUIDesigner=Open UI Designer
uiDesignerLabel=UI Designer
creatingNewForm=Creating new form...
switchTypeOfFormQuestionTitle=Form type incompatibility
switchTypeOfFormQuestion=The current form type for this task is {0}. A contract has been defined so you can use the UI designer to create a form that automatically contains the relevant widgets for the contract inputs. Do you want to use the UI designer to create a new form?
switchTypeOfFormQuestion=The current form type for this task is {0}. A contract has been defined so you can use the UI Designer to create a form that automatically contains the relevant widgets for the contract inputs. Do you want to use the UI Designer to create a new form?
internalFormMappingUndefined=Internal form mapping is undefined for {0}.
urlNotDefined=External URL form mapping is undefined for {0}.
formDoesntExistAnymoreMessage=The form {0} does not exist anymore. It may have been deleted from UI designer.
formDoesntExistAnymoreMessage=The form {0} does not exist anymore. It may have been deleted from UI Designer.
formDoesntExistAnymoreTitle=The form {0} does not exist anymore.
stepUIDesignerInfo=If the form has not yet been created, you are recommended to define the contract first.\nThis will enable generation of a form with the relevant widgets and data bindings for the contract inputs.\nIf you do not specify a form, a default form based on the contract is provided for development purposes.\nClick the pencil icon to edit the form, or use the dropdown list to map a different form.
processUIDesignerInfo=If the form has not yet been created, you are recommended to define the contract first.\nThis will enable generation of a form with the relevant widgets and data bindings for the contract inputs.\nIf you do not specify a form, a default form based on the contract is provided for development purposes.\nClick the pencil icon to edit the form, or use the dropdown list to map a different form.
......@@ -31,13 +31,13 @@ processURLInfo=Specify the URL of the form.\nThis must sent back information tha
overviewLegacyInfo=Go to the 6.x Application tab to define the overview page.
stepLegacyInfo=Go to the 6.x Application tab to define the task pageflow. The contract must be empty.
processLegacyInfo=Go to the 6.x Application tab to define the instantiation pageflow. The contract must be empty.
openUiDesignerInformationWindowTitle=UI designer information
openUiDesignerInformationMessage=You can use the UI designer to create and modify forms. To create a new form, we recommend that you first create a contract and then use the automatically generated form as your starting point, instead of creating the form from scratch.\nYou can also use the UI designer to create application pages and custom application layouts.
openUiDesignerInformationWindowTitle=UI Designer information
openUiDesignerInformationMessage=You can use the UI Designer to create and modify forms. To create a new form, we recommend that you first create a contract and then use the automatically generated form as your starting point, instead of creating the form from scratch.\nYou can also use the UI Designer to create application pages and custom application layouts.
openUiDesignerInformationToggleMessage=Do not show this dialog again.
hideEmptyContractDialogTitle=Empty contract
hideEmptyContractDialogMessage=This button generates a form with the relevant widgets and data bindings for the contract inputs. The mapping between the form is and this (task or process => 0) is done once for all. It is not updated when you update the contract. We recommend you create your contract before clicking on this button.\nDo you still want to open the UI designer?
hideEmptyContractDialogMessage=This button generates a form with the relevant widgets and data bindings for the contract inputs. The mapping between the form is and this (task or process => 0) is done once for all. It is not updated when you update the contract. We recommend you create your contract before clicking on this button.\nDo you still want to open the UI Designer?
hideEmptyContractDialogToggleMessage=Do not show this dialog again.
waitingForTomcatServer=Tomcat server is booting in background (this may take a few seconds)...
noForm=No form
noFormMessageOnTask=A human task with no form and no contract represents a manual task, completed outside Bonita BPM. The user will indicate in the application or Portal that the manual task is complete.\nA human task with a contract but no form expects the information needed to fulfill the contract to be provided programmatically.
noFormMessageOnProcess=This process will be instantiated programmatically (by a call activity or by an API call from an application, for example), so no form is necessary.\nWhen "No form" is selected, no default instantiation form is generated for testing.\nIf you have defined a contract and want to use the default form for testing, choose the UI designer option but do not specify a form.
noFormMessageOnProcess=This process will be instantiated programmatically (by a call activity or by an API call from an application, for example), so no form is necessary.\nWhen "No form" is selected, no default instantiation form is generated for testing.\nIf you have defined a contract and want to use the default form for testing, choose the UI Designer option but do not specify a form.
OpenPageDesigner=Open UI designer...
OpenPageDesigner=Open UI Designer...
EntryFormMapping=Form
CaseStartFormMapping=Instantiation form
OverviewFormMapping=Overview page
showLegacyMode=Show 6.x legacy features
showLegcyModeDescriptionPreferncePage=The 6.x legacy features enable you to continue to use forms that were created with {0} 6.x and imported into this version.\nThis is for backward compatibility and to ease migration.\nYou are recommended to migrate your process to take advantage of the 7.x features and use UI designer forms.\nWhen migration is complete, you no longer need to show the 6.x legacy features.
\ No newline at end of file
showLegcyModeDescriptionPreferncePage=The 6.x legacy features enable you to continue to use forms that were created with {0} 6.x and imported into this version.\nThis is for backward compatibility and to ease migration.\nYou are recommended to migrate your process to take advantage of the 7.x features and use UI Designer forms.\nWhen migration is complete, you no longer need to show the 6.x legacy features.
\ No newline at end of file
......@@ -227,10 +227,10 @@ catchMessageContentEventSectionDescription=A message is information sent from a
catchMessageEventCorrelationSectionDescription=Correlation keys are used to check that a message sent from a Send task is received by the Receive task of the relevant process instance. Define how to handle the correlation keys contained in a message that is received. The keys must already be defined in a Send task.
laneSectionDescription=A lane is a subdivision of a process. Lanes are usually used to group tasks that are carried out by a functional group or part of an organization. This means that all tasks in the lane can be assigned to the same actor. Therefore, it is good practise to name the lane with the name of the actor or functional group. You can also give a description.
looknfeelPropertySectionDescription=Legacy mode for backward compatibility.\nA look'n'feel definition sets the layout and style of forms created with the 6.x form designer.\nYou can modify an existing layout or template by modifying the HTML.
resourcePropertySectionDescription=Legacy mode for backward compatibility.\nThese resources are files used by the user interface to a 6.x process.\nYou can maintain the files used by your 6.x process, but we recommend that you migrate to using UI designer pages and forms, and define your application in {0}.
resourcePropertySectionDescription=Legacy mode for backward compatibility.\nThese resources are files used by the user interface to a 6.x process.\nYou can maintain the files used by your 6.x process, but we recommend that you migrate to using UI Designer pages and forms, and define your application in {0}.
parametersMappingSectionDescription=The mapping defines the relationship between variables in the parent process and variables in the called process.\nAuto map maps variables in the parent process to contract inputs of the called process, checking that data types are compatible. It uses variable name and data type to map called process variables to parent process variables.\nYou can update Auto map result. You can also define all the mappings manually, instead of using Auto map.
userXPSectionDescription=This is the information that is displayed about a task in the Portal. The estimated duration of the task is used to calculate the remaining time needed for the task after it has started. If you don't specify the Portal information, the name and description from the General pane are used.
confirmationPropertySectionDescription=Legacy mode for backward compatibility.\nThere is no need for a confirmation message in UI designer forms, because you define the navigation on success and on failure. You can maintain existing confirmation messages here, for use with 6.x forms.\nA confirmation message is shown at the end of a sequence of steps performed by one user, showing that no further actions are needed.
confirmationPropertySectionDescription=Legacy mode for backward compatibility.\nThere is no need for a confirmation message in UI Designer forms, because you define the navigation on success and on failure. You can maintain existing confirmation messages here, for use with 6.x forms.\nA confirmation message is shown at the end of a sequence of steps performed by one user, showing that no further actions are needed.
loopSectionDescription=Iteration means that a task or call activity is executed repeatedly until a condition is met. Specify the condition as an expression or a number of iterations. To execute multiple instances of the task at the same time, check Multi-instantiated. To execute multiple instances of the task one after another, check Standard loop. To execute the task once (no iteration) check None. To execute multiple instances of the task one after another, you can use Parallel multi-instance or Loop.
exportSuccessfullTitle=Export result
exportSuccessfullMsg=Look'n'feel exported successfully.
......@@ -319,6 +319,6 @@ assignToContractInput=Assigned to Contract Input
assignToData=Assigned to Data
targetParameterForOutput=Target data in called process
targetParameterForInput=Target in called process
sectionDescriptionOverviewForm=Legacy mode for backward compatibility.\nYou can maintain an existing overview here until it is migrated.\nYou can create an overview using the legacy tooling, but we recommend that you use the UI designer to create any new overview.\nThere is also a default overview page available if you choose the UI designer type.If you use a 6.x overview pageflow, go to Execution > Overview page and select the type 6.x
sectionDescriptionEntryForm=Legacy mode for backward compatibility.\nYou can maintain existing forms here until they are migrated.\nYou can create a form using the legacy tooling, but we recommend that you create a contract and use the UI designer to create any new form. If you use a 6.x form, go to Execution > Form and select the type 6.x
sectionDescriptionProcessEntryForm=Legacy mode for backward compatibility.\nYou can maintain existing forms here until they are migrated.\nYou can create a form using the legacy tooling, but we recommend that you create a contract and use the UI designer to create any new form. If you use a 6.x form, go to Execution > Instantiation form and select the type 6.x
sectionDescriptionOverviewForm=Legacy mode for backward compatibility.\nYou can maintain an existing overview here until it is migrated.\nYou can create an overview using the legacy tooling, but we recommend that you use the UI Designer to create any new overview.\nThere is also a default overview page available if you choose the UI Designer type.If you use a 6.x overview pageflow, go to Execution > Overview page and select the type 6.x
sectionDescriptionEntryForm=Legacy mode for backward compatibility.\nYou can maintain existing forms here until they are migrated.\nYou can create a form using the legacy tooling, but we recommend that you create a contract and use the UI Designer to create any new form. If you use a 6.x form, go to Execution > Form and select the type 6.x
sectionDescriptionProcessEntryForm=Legacy mode for backward compatibility.\nYou can maintain existing forms here until they are migrated.\nYou can create a form using the legacy tooling, but we recommend that you create a contract and use the UI Designer to create any new form. If you use a 6.x form, go to Execution > Instantiation form and select the type 6.x
......@@ -106,7 +106,7 @@ invalidMultipleFileContractInput=Invalid initial content for document {0}. A sin
invalidFileContractInputType=Invalid initial content for document {0}. A FILE contract input is expected but a {1} contract input has been found.
invalidSingleFileContractInput=Invalid initial content for document {0}. A multiple FILE contract input is expected but a single FILE contract input has been found.
missingFileContractInput=Invalid initial content for document {0}. No FILE contract input has been found.
emptyFormMappingWarning=UI designer form type is selected and no target form is defined for {0}. An autogenerated form will be used in the development environment ONLY.
emptyFormMappingWarning=UI Designer form type is selected and no target form is defined for {0}. An autogenerated form will be used in the development environment ONLY.
cannotUseThisStartEventTypeWithAContract=An instantiation contract cannot be used with this start event type. Use the none start event.
failedToRetrieveLeftOperandType=Failed to retrieve left operand type: {0}
methodDoesnotExistInLeftOperandType=The method {0}({1}) does not exist for {2}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment