| PI54586 |
Model rights - public / private components |
|
Component owners are now able to mark their component as ‘public’ - This implies that the component can be used freely by other companies in their integrations. Revoking the public status of the component is also always possible. The ‘publish’ and ‘revoke’ options are available from the Component page, if sufficient privileges are available. |
| PI52471 |
Develop sending e-mails when a request comes in |
|
For new model access requests and model access requests that are approved or denied, an e-mail notification system is added. This will speed up the processing time of model access requests, because the next responsible will be aware of the need for action. Please note that the e-mail notifications specified in PI52471 rely on the next update of Novulo Network (scheduled in April) and will therefore not be in place immediately after the update of the Application server. |
| PI53183 |
Develop a way to request read access to a MODEL you have no access to |
|
For getting access to a component that is not yet visible to you (because of missing access rights) there is a new procedure to get access based on the model number or GUID of the component you request access to. For this, use the ‘I can’t find the model I am looking for’ option in the model access request page and fill in the model number or GUID in the ‘model reference’ field. |
| PI53184 |
Develop a way to request read access to a COMPANY you have no access to |
|
For getting access to the models of a specific company that is not yet visible to you (because of missing access rights) there is a new procedure to get access based on the name of the company, some company’s employee’s e-mail address, or model number or GUID of a component of the company you request access to. For this, use the ‘I can’t find the company I am looking for’ option in the model access request page and fill in the company name, employee e-mail address, model number or GUID in the ‘company reference’ field. |
| PI54908 |
Implement mark down for documentation fields |
|
For reference architecture elements Concepts and Features the documentation field is now changed to Markdown format. Existing documentation will be transformed to Markdown for as much as possible. For the Processes and Enumerations a Markdown field is now also available for documentation |