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; } } }

Testing an xCP 2.0 app

Imran_Yusubov

Hello Experts,

How are we supposed to test an xCP 2.0 application. The old one had a debugging feature, though it was not very good but it was better than nothing. Now, I look at the new one and don't see anything for debugging testing or monitoring. Are we supposed to deploy the app every time whenever we make a simple modification and test it manually with our browser or is there a better way?

Thanks in advance

Find more posts tagged with

Comments

christopher.imes

Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.

You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for: "Documentum" and select the first result that appears. This will relocate it to the Developer Network space of the Documentum community.

Documentum

For further guidance on engaging with the communities for Documentum and related products, please refer to the

IIG Communities Getting Started Guide.

PanfilovAB

If you're asking about process debugger EMC has added it in xCP 2.1

dnvhariprasad

in xCP 2.1, you will also get "preview" feature where in you dont need to deploy the app everytime you make change which does not require changes in artifacts related to content server.