Visualisation and download of structured blocks

PreviousSpecial links into blocks to an object’s files NextFile and folder structure

Last updated 3 years ago

Was this helpful?

Visualisation and download of structured blocks

LIBSAFE allows you to visualize a structured block with different views: Textual, Visual, Style. To select the different options there is a link for each one as shown below:

The image above shows the Style view, only available if the type has a style sheet defined in its configuration.

To download a file with the block, there is the option to “Download raw XML”.

This functionality has a list of specific characteristics:

To access the Control Panel, it is necessary to have the configuring permissions according to the system profile.
For structured blocks, it is essential that the LXM code and the base tag, defined in the type, are well-formed, otherwise it will not be possible to create new blocks.
Text encoded in UTF8 format is mandatory in cases of massive text dump for structured blocks or containers for free blocks. The use of other encoding formats may result in a non-functional block.
If the system's internal and external tags match the user's own tags, it is necessary to change the tags in the section for all system variables. By default, the system uses the @@@ and (file) tags as internal and external.
The style sheet view will only be available if it has been defined in the Metadata Type creation that it will be used
The loading of large structured blocks will be conditioned by the performance of the server and the user's computer for the composition of the block in the interface. It is estimated that on average every 1000 lines of simple data takes 1 second, but for every additional 1000 lines a time load of 10% is applied. With a load of 40000 lines one can have a rendering timeout of 45 seconds.
Blocks cannot be edited or deleted after being stored, every time a block is managed, it becomes the latest version.
Sets cannot be edited after their creation, so it is recommended to use clear names and descriptions.
If it is possible that the payload file is created by an external platform and the file contains an encoded definition, it must be UTF8 with or without BOM only.

PreviousSpecial links into blocks to an object’s files NextFile and folder structure

Last updated 3 years ago

Was this helpful?

LIBSAFE allows you to visualize a structured block with different views: Textual, Visual, Style. To select the different options there is a link for each one as shown below:

The image above shows the Style view, only available if the type has a style sheet defined in its configuration.

To download a file with the block, there is the option to “Download raw XML”.

This functionality has a list of specific characteristics:

To access the Control Panel, it is necessary to have the configuring permissions according to the system profile.
For structured blocks, it is essential that the LXM code and the base tag, defined in the type, are well-formed, otherwise it will not be possible to create new blocks.
Text encoded in UTF8 format is mandatory in cases of massive text dump for structured blocks or containers for free blocks. The use of other encoding formats may result in a non-functional block.
If the system's internal and external tags match the user's own tags, it is necessary to change the tags in the section for all system variables. By default, the system uses the @@@ and (file) tags as internal and external.
The style sheet view will only be available if it has been defined in the Metadata Type creation that it will be used
The loading of large structured blocks will be conditioned by the performance of the server and the user's computer for the composition of the block in the interface. It is estimated that on average every 1000 lines of simple data takes 1 second, but for every additional 1000 lines a time load of 10% is applied. With a load of 40000 lines one can have a rendering timeout of 45 seconds.
Blocks cannot be edited or deleted after being stored, every time a block is managed, it becomes the latest version.
Sets cannot be edited after their creation, so it is recommended to use clear names and descriptions.
If it is possible that the payload file is created by an external platform and the file contains an encoded definition, it must be UTF8 with or without BOM only.