Best Of
Re: Default click Overview page
Have a look at FolderBrowserWidget2 (csui/integration/folderbrowser2/folderbrowser2.widget), if you want the click actions on documents be handled like on the Smart View page (/app). When compared to FolderBrowserWidget, FolderBrowserWidget2 recognises only connection/connector/context and start options and includes only show and destroy methods. FolderBrowserWidget2 supports features implemented as perspective navigations like Document Overview.
Document Overview.is implemented as perspective navigation. It destroyes the current perspective and creates and displays the perspective assigned to the target node. For documents it is a perspective showing the DocumentOverview widget.
FolderBrowserWidget was initially introduced to browse folders and download/upload document content. It does not provide features that were implemented later as perspective (Smart UI page) navigations. Depending on the feature, it will either fall back to an action that can be performed (acceptable, document, e.g.), or do nothing (bad, follow-up, e.g.).
FolderBrowseWidget2 internally uses PerspectiveContext and shows PerspectivePanelView like the Smart View page. That is why perspective navigations work there. While the content of FolderBrowserWidget remains for the widget's life, the content of FolderBrowseWidget2 may be destroyed and re-rendered depending on the perspective that is will display. While perspectives shown on the Smart View page or folders and other containers can be configured, FolderBrowserWidget2 shows only one common perspective for all containers - the NodesTable widget.
Document Overview.is implemented as perspective navigation. It destroyes the current perspective and creates and displays the perspective assigned to the target node. For documents it is a perspective showing the DocumentOverview widget.
FolderBrowserWidget was initially introduced to browse folders and download/upload document content. It does not provide features that were implemented later as perspective (Smart UI page) navigations. Depending on the feature, it will either fall back to an action that can be performed (acceptable, document, e.g.), or do nothing (bad, follow-up, e.g.).
FolderBrowseWidget2 internally uses PerspectiveContext and shows PerspectivePanelView like the Smart View page. That is why perspective navigations work there. While the content of FolderBrowserWidget remains for the widget's life, the content of FolderBrowseWidget2 may be destroyed and re-rendered depending on the perspective that is will display. While perspectives shown on the Smart View page or folders and other containers can be configured, FolderBrowserWidget2 shows only one common perspective for all containers - the NodesTable widget.
Re: DB migration for OpenText products
As far Content Server goes, there isn't any that's made available to you officially by OpenText. However, there is a third-party technology partner module from Syntergy, xDB for OpenText Content Server, that can help you with this move for a fee.
@Vijay_Sharma
@Vijay_Sharma
Re: How do I regenerate a token?
As a developer, you can manage your tokens from the Console access through OpenText | Developer. You'll only see that Console tab if your credentials are assigned the developer role.
From there, open up the application you want to regenerate the token for. On the right-hand side of the page, you'll see an area for managing your tokens.
Click on that button to open up the window. There, you can regenerate, revoke or configure redirect URLs for your token specific to that application.
From there, open up the application you want to regenerate the token for. On the right-hand side of the page, you'll see an area for managing your tokens.
Click on that button to open up the window. There, you can regenerate, revoke or configure redirect URLs for your token specific to that application.
KarOT
6
Re: Migration from one S3 object storage to another S3 storage
Since objects accessed via S3 is through url, you should be able to copy the contents to another bucket without issue (this is what migrate_content job would do). Before you actually do the copy, I would read the Documentum Admin (DA) guide on how to configure a new S3 store object from within DA. It will ask your for all the relevant bucket information for bucket c. After you copy the objects over bucket c, you will need to update a_storage_type for all the documents that are point to bucket B to point to bucket C. Note this attribute stores the name of the storage object created in DA (not necessarily name of bucket C).
Curious though, why are you creating a new bucket to begin with? You should be able to change the S3 storage type on existing bucket.
Curious though, why are you creating a new bucket to begin with? You should be able to change the S3 storage type on existing bucket.
Re: Default click Overview page
This is where you can Enable Document Overview Page when users clicks on a document Name - ?func=admin.documentoverview
Uldis
1