Page History
...
The content types that are stored in this structure are Reports, Dashboard tabs, Storyboards, and Views, Data transformation flows, and Stories.
Note |
---|
Ensure that you create both, a folder, and a sub folder before you save your content. |
Content Folders are managed through the Administration Console.
Anchor | ||||
---|---|---|---|---|
|
Folder Creation
This process shows how to create a parent folder, which can be used to store sub folders.
Styleclass | ||
---|---|---|
| ||
- Navigate to Administration > Administration Console from the left side navigation.
Expand the Content Folders tab. Click the Add button
To create a Content Folder, click the Add button under the Content Folders list in the Admin Console.
You will be taken to the Folder setup page, where you will need to define the following:
:Parameter Description Folder Name thisThis :will be the name of the folder displayed in various parts of the system when saving and viewing content. Description thisThis :will be the description of the folder, used to define its intended purpose and audience. Folder Hierarchy selectThis defines the level of the folder. Select : defaults to zero, provide a numeric sort order if you do not wish the folders to be'Top Level' to create a new parent folder. Sort Order (Advanced setting) Provide a numeric sort order to list the folders accordingly. For example, a sort order of 1 means the folder will be displayed first. Defaults to zero in which case the folders are sorted alphabetically. - Click
Click Submit
toto complete the
Folderfolder.
...
Next, create a sub folder. See the process below for further instructions.
Sub Folder Creation
Create a sub folder by following the steps below. Note that at least one folder should already be created.
Styleclass | ||
---|---|---|
| ||
- Once
...
- a folder has been created, click the Add button under the Content Folders list in the Admin Console to start defining Sub Folders.
- You will
...
- be taken to the same
...
- folder setup page. In the Folder Hierarchy field, select a parent folder where the sub folder will be created. A range of different options will become available..
Now that you are creating a sub folder, the following sections will need
...
to be defined. These relate to content settings and as such only correspond to the sub folder level, as the folder level can't directly contain content.
Folder Name: this will be the name of theParameter Description Folder Name Name of the sub : this will be the descriptionfolder displayed in various parts of the system when saving and viewing content. Description Description of the folder, used to define its intended purpose and audience. - Level: select the Sub Folder option. Once changed, a range of different options will become available.
- Parent Folder: select the Folder this Sub Folderwill be stored within.
- Draft Content Storage:
Folder Hierarchy This is used to select the parent folder within which this sub folder should exist. Advanced settings Expand this link to access additional advanced settings. These are discussed below. Sort Order Provide a numeric sort order to list the sub folders accordingly. For example, a sort order of 1 means the sub folder will be displayed first. Defaults to zero in which case the folders are sorted alphabetically. Draft Content Default Folder
Enabling this toggle means that any content that is not activated is automatically stored in this Sub Folder, such as draft reports, dashboards, etc. Note that Draftthere can be one default organiseddraft sub folder in the system, which will contain all draft content until a different sub folder has been selected by the content writer. This is used to keep all draft content in one place, making it easier to keep the system Note: enabling this option means that any content that is not activated is automatically stored in this Sub Folder. There can only be one Draft Storage folder.organized. - Sort Order: defaults to zero, provide a numeric sort order if you do not wish the folders to be sorted alphabetically.
- Status: when the Sub Folder is ready to be seen by users set the status to Active. When Draft only administrators will be able to view and edit it, and it can't be used for storage.
Now that the Level has been set to Sub Folder the following sections will need to be defined. These relate to content settings and as such only correspond to the sub folder level, as the folder level can't directly contain content.
Publish Access & Approvals
This section allows you to determine which users can publish public reports to the folder.
- If you select Users with Functional Access then all users with the public report function can write to this folder
- If you select Experts only or with Expert Approval then only specified users can publish reports into that folder. If a user does not have access to publish to that folder the report will be routed to an Expert for approval. This allows administrators and advanced users to approve all reports stored into the folder before they are activated for public consumption, ensuring they are correct and the data can be trusted.
Report Version History
...
Default View Folder Enable this toggle to define this sub folder to be used to store Views that are automatically created. Note that there can be only one of these folders in a system.
Version History The version history allows you to store the data returned in a report, in order to maintain historical result sets for reports.
- If version history is set to Current Version Only set then no historical results will be kept. This means that the system runs a database query, and creates a result set every time the report is run.
- If the Keep Historical Versions option is selected then all historical versions of the reports will be kept. With this option not only will the report definition saved but the data as well.
...
This allows users to view previous versions of the report and compare result sets.Note: It's important to remember that this option can quickly build up quite a large amount of data, so use this option sparingly.
All versions of the report data are stored in the Yellowfin Database. As the administrator you can determine how much history and the maximum size of reports you wish to save. This is an application management process that permits you to control the use of your infrastructure. Refer to the following parameters for more information.
...
Max Size Define the amount of storage available for caching report content in this folder (in KB). This lets you set a limit to the amount of report data that will be stored. If this limit is exceeded, the system will delete older cached content to store new one.
Max Versions Define the number of historical result sets that will be accessible, per report. For example, you can limit each report to store 20 result sets. If this number is exceeded, the system will delete older cached sets to store new one.
Note: Content folder limitations related to versions and age, do not apply if the content in question is used in a Story.
...
Version History
...
The version history allows you to store the data returned in a report.
If version history is set to Only keep the latest result set then no historical results will be kept.
If the Keep archived report result sets option is selected then all historical versions of the reports will be kept. Note: It's important to remember that this option can quickly build up quite a large amount of data, so use this option sparingly.
...
Max Size
...
The maximum size for data to be saved in cache or in the database where version history is required.
...
Max Items Displayed
...
The maximum number of items to be displayed on the history drop down list for management information reports.
...
Delete Period
...
After what period of time should archived reports be deleted.
Max Age Define how long the historical result sets should be stored before they are deleted. For example, if you define this age limit to be 5 years, then content will be stored for 5 years; all older content will be deleted.
Note: This limitation will not apply if the content in question is used in a Story.
- Next, you can define the security access and approval settings for the content that will be created in this sub folder. Refer to the sub section below.
Anchor | ||||
---|---|---|---|---|
|
Content Approval and Security Access
This section allows you to configure an expert approval process for the content stored in this folder, as well as define which users can access the content.
- After providing details of the sub folder, click the User Access tab.
- Enable the Expert Approval Required to Publish toggle to define an approval process for content created in this folder. This allows administrators and advanced users to approve all reports or other content stored into the folder before they are activated for public consumption, ensuring they are correct and the data can be trusted.
- Then select a user or group in the Person/Group panel, to be the expert approver of the content.
Sub Folders can also
...
Content Security Access
...
be secured to restrict access to the content they contain based on specified permissions. The options for setting the security are as follows:
Unsecure Content: peopleSecurity setting thisDescription Unsecure People can access onthe content stored here without logging Secure: usersin. logonPublic Users will have to Access Security Level Required: onlylog in before being able to view the content, but all users of the system will be able to view it. Private Only selected users will be able to access this content. - If you choose
...
- Private, then you must
...
- select a person or group and then the level of access that they are permitted.
Click on the access level of the selected user (or approver) to update their level of access. Three types of access exist:
Access Level Description Read Users will only be able to read the content but not create new items of this type of content. Edit
...
If a content item exists a user will be able to edit and update an existing piece of content but not create new or delete items in this folder. They will also be able to read all content in this folder. Delete Users with delete access will be able to read, edit, create and delete content of this type. You must have at least one person with delete access
...
Note:
...
if you want all your users to be able to read the item make sure you have a group created with all your users. Use this group for read access.
...
- You can have as many groups and people in the list as you wish. You cannot finish the process if you do not have at least one person or group with delete access. Select a person with delete access to finish.
- Once done, click Submit to save changes.
Primary Org Content Security
When using Client Org functionality, you are able to secure Content Sub Folders content sub folders at the Primary Org primary org by assigning access to User Groups user groups created at the Client Org client org level. This will allow Administrators administrators to restrict Primary Org primary org content to specified users in each Client Orgclient org, rather than all Primary Content primary content being available to all Client Org client org users.
Edit Folder/Sub Folder
...
To make changes to a Folder or Sub Folder, simply locate it on the Admin Console page and click on its name.
...
To delete a Folder or Sub Folder, simply locate it on the Admin Console page and click on the x next to it in the list.
...