Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS-7134] Clarifications for types #1247

2 changes: 1 addition & 1 deletion content-accelerator/latest/configure/admin-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -537,7 +537,7 @@ Additional Viewer Configurations:
Renditioning:

* Elevate Renditioning Priority for Folder
* Enable View Time Renditioning
* Enable View Time Renditioning - Enable this option if types utilized in this trac do not have the `tsg:renditioned` aspect applied and require view time renditioning functionality. Note that all ACA Accelerator types are pre-configured with the `tsg:renditioned` aspect and do not require view time renditioning. Therefore, you only need to enable this option for out of the box accelerator types.
* Rendition Check Period

Configure:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,11 @@ To add custom alfresco models you will need to define a bean that has a parent o
</property>
</bean>
```
When you add a new document type extension for use in Alfresco Content Accelerator, we recommend including the `tsg:renditioned` mandatory aspect. This aspect provides streamlined handling of PDFs renditions for viewing and includes:

* Immediate renditioning to PDF upon document upload or version
* Separate renditions for each version of the node in Alfresco

> **Note:** In many ACA Policy and Procedure implementations, dedicated per-version renditions are a regulatory requirement.

If, however, the `tsg:renditioned` aspect is not desired, or the model already exists and cannot be updated, it is possible to turn on view time renditioning in the Document Viewer config in the Stage.
Prosune marked this conversation as resolved.
Show resolved Hide resolved
20 changes: 5 additions & 15 deletions content-accelerator/latest/install/install-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -679,25 +679,15 @@ This section walks through how to install the web applications on Alfresco Tomca

Obtain the `default-{accelerator}.zip` for your accelerator and rename the zip to `default.zip`.

5. Import default configuration. There are two ways you can do this.
5. Import default configuration using config import tool.

OPTION 1 - use the config import tool (This may not be available on initial install):
1. In a browser, navigate to {Application Base URL}/ocms and login to the application as the Alfresco Administrator. The screen displays a message that no configurations exist for the application yet.

* In a browser navigate to `{Application Base URL}/ocms/admin/ConfigArchiver` and login to the application as the Alfresco Administrator.
2. Click the button that is included in the message to navigate to the administration interface.

* Use the *Import Config* function to import the `default.zip` from the last step.
3. Navigate to **Tools** > **Config Archiver** from the left menu.

OPTION 2 - upload the configs via share:

* In a browser navigate to `{Application Base URL}/share` and login to the application as the Alfresco Administrator.

* Navigate to the repository and into the folder `hpi`

* Drag and drop the `default.zip` into this location

* Delete all contents of the current `default` folder

* Click on the `default.zip` and choose the "unzip to" action, select the `repository> hpi> default` folder
4. Use the Import Config function to import the default.zip from the previous step.

6. (OPTIONAL) This step is only required if **NOT** using the Alfresco Enterprise Viewer:

Expand Down