Page Comparison

Page Properties

hidden	true
id	REFACTURE

Product Version	2020 Autumn
Report Note	published
Assignee	Kolibri

Resources & Remarks

Is this really a conceptual article - it reads more like a tutorial. Can you please come back to me to check the best location. Thx Inga
Please use the prepared templates to create new articles ...

Modification History

Name	Date	Product Version	Action
Antje	08 FEB 2021	2.4	New page properties macro.

Im Bereich der Beschreibung für den LeadingType gibt es mit der 2021 Autumn Alpha2 ein neues Feature:

In der Summary werden unter Characteristika alle einem Objekt zugewiesenen SOTs lokalisiert angezeigt, so dass der Anwender sehen kann, was das Objekt insgesamt ausmacht. In der Regel sind aber auch eher systemische Objekttypen dabei, wie eben der Typ appClientsystem:leadingType oder der für die beiden Felder Titel und Beschreibung mit appClient:clientdefaults. Es ist nun möglich, solche SOTs dort nicht mehr anzuzeigen. Dafür werden sie dann zur Eigenschaft 'classification:systemsot' im administrativen Bereich unlokalisiert sichtbar gemacht. Damit das funktioniert, muss eine SOT das classification-Tag 'systemsot' hinzugefügt werden.

Story:https://jira.optimal-systems.de/browse/COOL-14997

...

Code Block

language	xml
title	Default Schema 'Client'	collapse	true

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<schema xmlns="http://optimal-systems.org/ns/dmscloud/schema/v5.0/">
	<propertyStringDefinition>
        <id>clienttitle</id>
        <propertyType>string</propertyType>
        <cardinality>single</cardinality>
        <required>true</required>
        <maxLength>200</maxLength>
    </propertyStringDefinition>
    <propertyStringDefinition>
		<id>clientdescription</id>
		<propertyType>string</propertyType>
		<cardinality>single</cardinality>
		<required>true</required>
		<maxLength>200</maxLength>
	</propertyStringDefinition>
    <typeDocumentDefinition>
        <id>minidoc</id>
        <baseId>system:document</baseId>
        <contentStreamAllowed>allowed</contentStreamAllowed>
        <secondaryObjectTypeId>appClientsystem:leadingType</secondaryObjectTypeId>
        <secondaryObjectTypeId>appClient:clientdefaults</secondaryObjectTypeId>
    </typeDocumentDefinition>
	<typeSecondaryDefinition>
		<id>clientdefaults</id>
		<description>contains title and description fields mainly for mixed resultlist and object header</description>
		<baseId>system:secondary</baseId>
		<propertyReference>clienttitle</propertyReference>
		<propertyReference>clientdescription</propertyReference>
        <classification>appClient:required</classification>
        <classification>appClient:create:false</classification>
	</typeSecondaryDefinition>
</schema>

...

Code Block

language	xml
title	Schema 'Clientsystem'	collapse	true

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<schema xmlns="http://optimal-systems.org/ns/dmscloud/schema/v5.0/">
    <propertyStringDefinition>
		<id>leadingTypeId</id>
		<propertyType>string</propertyType>
		<cardinality>single</cardinality>
		<required>false</required>
	</propertyStringDefinition>
	<typeSecondaryDefinition>
		<id>leadingType</id>
		<description>contains the field that supports a better use of FSOTs</description>
		<baseId>system:secondary</baseId>
		<propertyReference>leadingTypeId</propertyReference>
        <classification>appClient:create:false</classification>
        <classification>appClient:search:false</classification>
	</typeSecondaryDefinition>
</schema>

...

Code Block

language	xml
title	Example for using FSOTs	collapse	true

	<typeDocumentDefinition>
		<id>preemail</id>
		<description>...</description>
		<baseId>system:document</baseId>
        <classification>appClient:search:false</classification>
        <classification>appClient:create:false</classification>
		<contentStreamAllowed>required</contentStreamAllowed>
        <secondaryObjectTypeId>appClientSystem:leadingType</secondaryObjectTypeId>
        <secondaryObjectTypeId static="false">appClient:clientdefaults</secondaryObjectTypeId>
        <secondaryObjectTypeId static="false">emailsot</secondaryObjectTypeId>
    </typeDocumentDefinition>
    <typeSecondaryDefinition>
        <id>emailsot</id>
        <baseId>system:secondary</baseId>
		<propertyReference>from</propertyReference>
		<propertyReference>to</propertyReference>
		<propertyReference>cc</propertyReference>
		<propertyReference>subject</propertyReference>
		<propertyReference>hasattachment</propertyReference>
		<propertyReference>attachmentnames</propertyReference>
		<propertyReference>received</propertyReference>
        <classification>appClient:primary</classification>
    </typeSecondaryDefinition>

...

Classification tag Field type / Object tpye Description

email

string

An e-mail button is displayed that allows opening the installed e-mail client with the e-mail address specified.

The entered value is validated with help of an internal browser function. Valid addresses are those following the standard specifications → wikipedia

This e-mail field is displayed both in the Summary aspect and the result list column.

Note
Values like "Mike Johnson" <mike.johnson@mycompany.com> result in case rendering problems. Make sure that only 'mike.johnson@mycompany.com' is used.

url

string

A URL button is displayed that allows opening the URL specified in a browser.

The entered value is validated with the help of an internal browser function. Valid addresses are those following the standard specifications → wikipedia

This URL field is displayed both in the Summary aspect and the result list column.

phone

string

A phone button is displayed that allows opening the number specified in the phone application available. In the Chrome browser a connected Android phone can be used.

No validation takes place.

This phone field is displayed both in the Summary aspect and the result list column.

id:organization

string

The organization field offers a list of found users while typing characters. The user ID is stored while the user name is shown in a chip.

This field is displayed both in the Summary aspect and the result list column.

id:reference[]

id:reference[myObjectTypeId,...]

string

The reference field offers a list of found objects while typing characters. The object ID is stored while its title is shown in a chip. The object can be opened with a click on the anchor icon. If a referenced object does not have a title, its object ID is shown instead.

A list of technical object type names allows filtering the possible results. An empty list allows searching all object types.
Restrictions: The system types system:object, system:folder, and system:documents are not supported. In case, all object types should be affected keep the list empty (but brackets are needed!)

This field is displayed in both the Summary aspect and the result list column.

catalog[new,draft,review,released,rejected] string This is the configuration of a simple static catalog. Users of any tenant can only select the values specified in the list. Only one language is supported here.

digit number If this tag is not specified, no digital grouping takes place. Otherwise, numbers are rendered with a delimiter as 123,456,789.35 instead of 123456789.35.

tag[myttagname,0,1]
tag[anothertagname,0,10,20,30]

object type

Beginning with version 2020 Winter aka 2.4, system tags can be used for filtering and for display as a result list column in the reference client. Tags can be assigned to any object without any predefinition, so it is necessary to define them. Use a classification tag that is part of the object type definition you want to display the tag.

Restriction: In the case of FSOTs you need to use the classification tag for each of them. Beginning with 2021 Autumn the classification tag specified for the object type that references the FSOTs is inheriting the classification tag.

The values of tags can be localized. Tag values are numbers that are not meaningful to the user. yuuvis® architect provides a key for each tag and its value to be localized in the following format: mytagname, mytagname:0, ... mytagname:5. The tag name can contain only lower-case characters and ':', which allows you to use prefixes just like in app schemas.

You can read about tagging of objects here: Tagging

...

Versions Compared

Old Version 4

New Version Current

Key