nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customisation Needed in Teamsite

manpreet1

Hello Team,

We are using TS Version 6.7 SP-1

We have the following web server environment

- Development server
- staging server
- Production server.

We have configured the teamsite deployment in the form of customize workflows. On selecting the files, this workflow pushes the files to development environment first, staging environment in the next step and production environment in the last step.

Requirement: We want to add an additional tab in the teamsite (workarea level) displaying the status of deployment of each file to our web server. Currently as shown in the screenshot the columns displayed are “Name”,”Modified by” ,”Modified”. We would like to add two more columns “Staging deployment date” and “Production deployment date”

However the main requirement is how to capture these timestamps? Is there already default functionality available with teamsite to get this information?

Any pointers would be highly appreciated.
Thanks in advance!

Regards,
Manpreet

Find more posts tagged with

Comments

Adam Stoller

Hello Team,

We are using TS Version 6.7 SP-1

We have the following web server environment

- Development server
- staging server
- Production server.

We have configured the teamsite deployment in the form of customize workflows. On selecting the files, this workflow pushes the files to development environment first, staging environment in the next step and production environment in the last step.

Requirement: We want to add an additional tab in the teamsite (workarea level) displaying the status of deployment of each file to our web server. Currently as shown in the screenshot the columns displayed are “Name”,”Modified by” ,”Modified”. We would like to add two more columns “Staging deployment date” and “Production deployment date”

However the main requirement is how to capture these timestamps? Is there already default functionality available with teamsite to get this information?

Any pointers would be highly appreciated.
Thanks in advance!

Regards,
Manpreet

The first thought that comes to mind is the use of metadata on the assets to record when they were deployed to each environment and then customize the file list to extract that metadata from the files for presenting in that list -- however:

" - which would seem to render my previous suggestion of using EAs as moot. I haven't bothered to read the documentation on this thoroughly - but it seems you need to find some way to make the information you want into a "property". Perhaps someone else here has done something similar and can provide some pointers?

Baracus

I've used something similar to Ghoti's suggestion, where file and deployment related data was captured and stored as extended attributes. We simply created a "Details" tab on the DCT, and displayed all of the relevant data in read only fields.

This particular design was part of our content re-use model. It was used to amalgamate records/assets, and distribute them to a subset of branches and targets. Therefore, it was easy for a client to access details of any particular data push.

Food for thought, good luck.

ISCBorisB

I've used something similar to Ghoti's suggestion, where file and deployment related data was captured and stored as extended attributes. We simply created a "Details" tab on the DCT, and displayed all of the relevant data in read only fields.

This particular design was part of our content re-use model. It was used to amalgamate records/assets, and distribute them to a subset of branches and targets. Therefore, it was easy for a client to access details of any particular data push.

Food for thought, good luck.

The weakness of this solution is that the changes in the asset Status are kept in the asset itself.
That forces a need to maintain a DCR in the writable area and much worse, to modify it even when *real*
DCR data did not change. That in turn throws off DCR history, etc.

The way it has been explained to us, "Status" is more like DCR - WF Relation or "reach link", to steal
from the DB terminology. If so, we can use many-to-many Link Table approach. For example, create a dedicated
tracking structure ( DCR perhaps? That'll give standard GUI + Server side access for free ) that will maintain
status per Entry, related Dates, WF IDs, whatever you need. WFs then can modify Tracker automatically and
authorised personnel from GUI.

Just my two cents

new_report_1.rptdesign

Baracus

The weakness of this solution is that the changes in the asset Status are kept in the asset itself. That forces a need to maintain a DCR in the writable area and much worse, to modify it even when *real* DCR data did not change. That in turn throws off DCR history, etc.

Granted, but our solution was more of a simplified version of your recommendation. We used a seperate content/data type to build and track deployments. These "deployment" records allowed us to maintain deployment related information (in the deployment DCR only, some of which were EAs), while preserving the integrity of the assets we were deploying.

Adam Stoller

The weakness of this solution is that the changes in the asset Status are kept in the asset itself.
That forces a need to maintain a DCR in the writable area and much worse, to modify it even when *real*
DCR data did not change. That in turn throws off DCR history, etc.

The way it has been explained to us, "Status" is more like DCR - WF Relation or "reach link", to steal
from the DB terminology. If so, we can use many-to-many Link Table approach. For example, create a dedicated
tracking structure ( DCR perhaps? That'll give standard GUI + Server side access for free ) that will maintain
status per Entry, related Dates, WF IDs, whatever you need. WFs then can modify Tracker automatically and
authorised personnel from GUI.

Just my two cents

I agree that a DB-type solution would probably be best here - but the original request had to do with modifying the GUI file list to contain columns with this information - and I'm just not sure how (if) one can do that with the existing UITK - since it seems to rely on "properties" and not coded functions.

I think a custom tab and/or custom menu item that utilizes information stored within a DB for tracking the dates of deployment for any given asset and/or the group of assets deployed to a particular environment on any given date - is probably much more easily implemented, and probably better over-all, but it doesn't meet the requirements as stated.

So - I think part of the question here is: Is it possible to meet those requirements? If not, then the alternatives discussed here are probably worth pursuing.