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

Customizing Teamsite default error message

ivanho

Hi,

Does anyone know where can i change the message thrown by Teamsite ?

Eg: The form entry ABC.xml already exists and is currently in use.
Java null pointer exception

Find more posts tagged with

Comments

Adam Stoller

Hi,

Does anyone know where can i change the message thrown by Teamsite ?

Eg: The form entry ABC.xml already exists and is currently in use.
Java null pointer exception

Basic answer:

supported.If there's something you think is just flat out bad or wrong - you can open a ticket with Support, but I wouldn't hold my breath waiting for it to get fixed...Of of curiosity - what were you hoping to change that message to say?

ivanho

Ghoti:

It is a message from application. We have business users using the system and java null exception for them is not friendly enough.

I think is better to log a support ticket to clarify on the voiding of support / semi-support contract.

Investigator_List_by_Indication (7).xls

Adam Stoller

Ghoti:

It is a message from application. We have business users using the system and java null exception for them is not friendly enough.

I think is better to log a support ticket to clarify on the voiding of support / semi-support contract.

I agree that opening a Support case makes sense if it is the application - but what is the context of when that message appears?

I.e.: If it is coming as part of a custom workflow or a custom DCT, etc. - then it is probably the result of custom code and your case may get rejected based on that fact.

On the other hand, if it happens when browsing a branch or something clearly resulting from OOTB functionality - then your case has much more credence.

ivanho

It is thrown from application.

Let say I have Branch A and Branch B.

My .page in Branch A is pointing to a content DCR in Branch B. After I submit the page to a custom workflow, and click anywhere in Content Center, the java null exception will be shown.

Let's give it a try with Support@interwoven.com Smiley Happy

Adam Stoller

My .page in Branch A is pointing to a content DCR in Branch B. After I submit the page to a custom workflow, and click anywhere in Content Center, the java null exception will be shown.

I assume you mean a custom PLC (Publish LiveSite Content) workflow - yes?
Can you replicate the problem using the OOTB PLC workflow?

If not - the problem is probably in your custom workflow somewhere and thus reprepsents an issue that is less-likely to be addressed by support. You may have to deconstruct / reconstruct your customizations to try to narrow down the source of the issue.