censhare Documentation

… Learn how to use, administrate, customize, and develop the censhare Omnichannel Content Management Platform. What's new in censhare censhare WP CI HUB User Guid …
https://documentation.censhare.com/censhare-2021/en

Time zone support for project management

… Teams can be distributed in various locations in different countries and even continents. censhare supports time zones for projects and tasks, when they are ass …
https://documentation.censhare.com/censhare-2021/en/user-guide/manage-projects/time-zone-support-for-project-management

The simple DAM workspace

… The censhare DAM Starter Kit provides a simplified, intuitive user interface to get started with Digital Asset Management (DAM) in censhare Web. An overview on …
https://documentation.censhare.com/censhare-2021/en/user-guide/get-started/get-to-know-your-workspace/the-standard-workspace/the-simple-dam-workspace

Store, share & manage searches

… Save your common searches to execute them with one click. Group and organize your searches. Share your searches with other users. Context You can save any searc …
https://documentation.censhare.com/censhare-2021/en/user-guide/manage-assets/search-filter-assets/store-share-manage-searches

Import and export assets (censhare Client)

… Import and export assets in the censhare Client. Server actions transfer assets or asset structures between censhare systems. Target group Power users Solution …
https://documentation.censhare.com/censhare-2021/en/user-guide/manage-assets/upload-files-create-assets/import-and-export-assets-censhare-client

Password server actions

… The password server actions are part of the user management setup. Create Person assets When a new user logs in for the first time, censhare creates a person as …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/security-management/define-password-policies/password-server-actions

XML Editor - Create variables

… Variables can be created in the XML editor with the xe:variable widget. Overview You can store the result of an XPath expression in a variable and use it in oth …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/xml-editor-create-variables

censhare Client customization

… Learn how to customize the censhare Client (java-based desktop client). icon related-topics Optionally, assign a Font Awesome icon to the page. Enter the class …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization

Modes in Content Editor and Article Editor

… Quick overview of the custom-content-handler elements. Attributes Handler "asset" Possible values: Abb1.jpg Example of default mode "ID" – View of Content-Ed< xi:include xmlns:xi = "http://www.w3.org/2001/XInclude" href = "censhare:/service/assets/asset/id/675233/version/3/transform;key=transform:article-asset-to-group;format=xml" element-name = "group" /><__select__/>< xi:include xmlns:xi = "http://www.w3.org/2001/XInclude" href = "censhare:/service/assets/asset/id/675233/version/3/transform;key=transform:article-asset-to-group;format=xml" element-name = "group" /><__select__/>< xi:include xmlns:xi = "http://www.w3.org/2001/XInclude" href = "censhare:/service/assets/asset/id/675233/version/3/transform;key=transform:article-asset-to-group;format=xml" element-name = "group" /><__select__/>< xi:include xmlns:xi = "http://www.w3.org/2001/XInclude" href = "censhare:/service/assets/asset/id/675233/version/3/transform;key=transform:article-asset-to-group;format=xml" element-name = "group" /><__select__/> …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/modes-in-content-editor-and-article-editor

XML Editor - Auto-completion field

… The auto-completion field is a widget for the XML editor that can be used as an alternative to a pop-up menu widget. Overview The auto-completion fields allows < xe:auto-completion-field source = " " search-value-source = " " internal-search = " " popup-row-height = " " popup-row-width = " " css-key = " " expression-id = " " max-items = " " >< xe:options value-key = " " label-key = " " option-label-expression = " " lookup-expression = " " >< xe:generator expression = " " />< xe:auto-completion-field label = "${workflow-target}" label- style =" label-default " width = "30em" 
 source = "@wf_target" sort = "ascending" >< xe:options label-key = "@display_name" value-key = "@id" >< xe:generator name = "filtered_cachedtables" table-name = "party" source = "@isvisible" match = "1" />< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" width = "200" max-items = "1000" >< xe:options label-key = "@name" option-label-expression = " =:concat(asset/@name, ', ', asset/@id)" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" /><500). Example 3 Auto-completion field to select image assets. The ID of the selected asset is written in an asset feature of the type "asset reference". The generator runs an asset query on the censhare server using an XPath query. In contrast to the second example - here the filtering by the input value is not carried out by the client locally, but rather passed as part of the XPath query to the server. This option should always be used when the expected result set (assets) might be large (approximately >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" search-value-source = "$temp@search" width = "200" popup-row-height = "50" popup-row-width = "250" max-items = "100" >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" css-key = "asset-info" expression-id = "asset-ref-list" width = "200" max-items = "1000" >< xe:options label-key = "@name" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" />< xe:auto-completion-field source = " " search-value-source = " " internal-search = " " popup-row-height = " " popup-row-width = " " css-key = " " expression-id = " " max-items = " " >< xe:options value-key = " " label-key = " " option-label-expression = " " lookup-expression = " " >< xe:generator expression = " " />< xe:auto-completion-field label = "${workflow-target}" label- style =" label-default " width = "30em" 
 source = "@wf_target" sort = "ascending" >< xe:options label-key = "@display_name" value-key = "@id" >< xe:generator name = "filtered_cachedtables" table-name = "party" source = "@isvisible" match = "1" />< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" width = "200" max-items = "1000" >< xe:options label-key = "@name" option-label-expression = " =:concat(asset/@name, ', ', asset/@id)" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" /><500). Example 3 Auto-completion field to select image assets. The ID of the selected asset is written in an asset feature of the type "asset reference". The generator runs an asset query on the censhare server using an XPath query. In contrast to the second example - here the filtering by the input value is not carried out by the client locally, but rather passed as part of the XPath query to the server. This option should always be used when the expected result set (assets) might be large (approximately >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" search-value-source = "$temp@search" width = "200" popup-row-height = "50" popup-row-width = "250" max-items = "100" >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" css-key = "asset-info" expression-id = "asset-ref-list" width = "200" max-items = "1000" >< xe:options label-key = "@name" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" />< xe:auto-completion-field source = " " search-value-source = " " internal-search = " " popup-row-height = " " popup-row-width = " " css-key = " " expression-id = " " max-items = " " >< xe:options value-key = " " label-key = " " option-label-expression = " " lookup-expression = " " >< xe:generator expression = " " />< xe:auto-completion-field label = "${workflow-target}" label- style =" label-default " width = "30em" 
 source = "@wf_target" sort = "ascending" >< xe:options label-key = "@display_name" value-key = "@id" >< xe:generator name = "filtered_cachedtables" table-name = "party" source = "@isvisible" match = "1" />< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" width = "200" max-items = "1000" >< xe:options label-key = "@name" option-label-expression = " =:concat(asset/@name, ', ', asset/@id)" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" /><500). Example 3 Auto-completion field to select image assets. The ID of the selected asset is written in an asset feature of the type "asset reference". The generator runs an asset query on the censhare server using an XPath query. In contrast to the second example - here the filtering by the input value is not carried out by the client locally, but rather passed as part of the XPath query to the server. This option should always be used when the expected result set (assets) might be large (approximately >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" search-value-source = "$temp@search" width = "200" popup-row-height = "50" popup-row-width = "250" max-items = "100" >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" css-key = "asset-info" expression-id = "asset-ref-list" width = "200" max-items = "1000" >< xe:options label-key = "@name" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" />< xe:auto-completion-field source = " " search-value-source = " " internal-search = " " popup-row-height = " " popup-row-width = " " css-key = " " expression-id = " " max-items = " " >< xe:options value-key = " " label-key = " " option-label-expression = " " lookup-expression = " " >< xe:generator expression = " " />< xe:auto-completion-field label = "${workflow-target}" label- style =" label-default " width = "30em" 
 source = "@wf_target" sort = "ascending" >< xe:options label-key = "@display_name" value-key = "@id" >< xe:generator name = "filtered_cachedtables" table-name = "party" source = "@isvisible" match = "1" />< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" width = "200" max-items = "1000" >< xe:options label-key = "@name" option-label-expression = " =:concat(asset/@name, ', ', asset/@id)" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" /><500). Example 3 Auto-completion field to select image assets. The ID of the selected asset is written in an asset feature of the type "asset reference". The generator runs an asset query on the censhare server using an XPath query. In contrast to the second example - here the filtering by the input value is not carried out by the client locally, but rather passed as part of the XPath query to the server. This option should always be used when the expected result set (assets) might be large (approximately >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" search-value-source = "$temp@search" width = "200" popup-row-height = "50" popup-row-width = "250" max-items = "100" >< xe:auto-completion-field source = "asset_feature[feature= 'mf:asset-ref2',value_long2= '0']@value_asset_id" css-key = "asset-info" expression-id = "asset-ref-list" width = "200" max-items = "1000" >< xe:options label-key = "@name" value-key = "@id" >< xe:generator expression = " =:cs:asset()[@censhare:asset.type= 'picture.*']" /> …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/xml-editor-auto-completion-field

Create entries in pop-up or auto-completion fields

… Within a pop-up or in the auto-completion field, a new asset or asset feature can now be generated. Introduction If text exists in the text entry field, then an …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/create-entries-in-pop-up-or-auto-completion-fields

Asset feature customization

… Asset properties such as metadata and product features are stored in asset features. The censhare standard configuration contains a wide range of preconfigured …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/asset-feature-customization

Customize column sorting

… Find solutions on typical sorting issues: It is not possible to sort a column. The sorting of a column delivers wrong results. Sorting is not possible Reason Th< xe:column key = "workflow-target" label = "${ workflow-target} " sortable = "false" width = "150" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sorting-source = "@wf_target" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sortable = "false" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "filesize" label = "${ file-size} " sortable = "false" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "filesize" label = "${ file-size} " sorting-source = "storage_item[key= 'master']@filelength" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then cs:format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "page" type = "number" label = "${ page} " width = "50" align = "right" sortable = "true" sorting-source = "CUSTOM:function.sorting" formula = ":if (//@first_paging) then cs:format-number((//@first_paging), '#') else ()" />< xe:column key = "workflow-target" label = "${ workflow-target} " sortable = "false" width = "150" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sorting-source = "@wf_target" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sortable = "false" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "filesize" label = "${ file-size} " sortable = "false" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "filesize" label = "${ file-size} " sorting-source = "storage_item[key= 'master']@filelength" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then cs:format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "page" type = "number" label = "${ page} " width = "50" align = "right" sortable = "true" sorting-source = "CUSTOM:function.sorting" formula = ":if (//@first_paging) then cs:format-number((//@first_paging), '#') else ()" />< xe:column key = "workflow-target" label = "${ workflow-target} " sortable = "false" width = "150" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sorting-source = "@wf_target" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sortable = "false" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "filesize" label = "${ file-size} " sortable = "false" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "filesize" label = "${ file-size} " sorting-source = "storage_item[key= 'master']@filelength" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then cs:format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "page" type = "number" label = "${ page} " width = "50" align = "right" sortable = "true" sorting-source = "CUSTOM:function.sorting" formula = ":if (//@first_paging) then cs:format-number((//@first_paging), '#') else ()" />< xe:column key = "workflow-target" label = "${ workflow-target} " sortable = "false" width = "150" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sorting-source = "@wf_target" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "workflow-target" label = "${workflow-target} " width = "150" sortable = "false" formula = ":cs:cachelookup('party', '@id', asset/@wf_target)/@display_name" />< xe:column key = "filesize" label = "${ file-size} " sortable = "false" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "filesize" label = "${ file-size} " sorting-source = "storage_item[key= 'master']@filelength" align = "right" width = "80" formula = ":if (asset/storage_item[@key= 'master']) then cs:format-number((sum(asset/storage_item[@key= 'master']/@filelength) + 52429) div 1048576, '#,##0.0 MB') else ' ' " />< xe:column key = "page" type = "number" label = "${ page} " width = "50" align = "right" sortable = "true" sorting-source = "CUSTOM:function.sorting" formula = ":if (//@first_paging) then cs:format-number((//@first_paging), '#') else ()" /> …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/customize-column-sorting

XML Editor - Image Crop widget

… This XML Editor widget defines an image section in pixel with X, Y coordinates for upper left corner, width and height. Introduction In the first step, the widg …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/censhare-client-customization/xml-editor-image-crop-widget

Set feature relevance

… Define the relevance of an asset feature in percent. Overview For each asset feature, a relevance value can now be optionally specified. To do so, open the feat …
https://documentation.censhare.com/censhare-2021/en/administrator-guide/asset-feature-customization/create-asset-features/set-feature-relevance