Mandatory Link Field for RRC
Accepted answer
Currently the built-in process support in RRC/RDNG is not this advanced, so there isn't a declarative / configurable way to impose this dependency before saving.
But I think you could address this requirement by running an "audit check" in a couple of different ways:
But I think you could address this requirement by running an "audit check" in a couple of different ways:
- Use the new JavaScript extension to identify any requirements that lack this link. It may be possible to have it alert the user when saving the artifact.
-
Use a saved view that includes a combination of relevant artifact type(s) and the link type that must exist; include in the view a sort that puts any artifacts with missing links at the top of the results.
2 other answers
Hi Canberk,
using WAS to host your extensions files is not an easy choice as it is not designed to providing simple hosting of static content. I believe most deployments of WAS also include a separate web server (perhaps Apache or IHS) and this is more likely to be where you would want to put your static content.
This article provides some insight into your options http://www.ibm.com/developerworks/websphere/techjournal/0211_brown/brown.html.
using WAS to host your extensions files is not an easy choice as it is not designed to providing simple hosting of static content. I believe most deployments of WAS also include a separate web server (perhaps Apache or IHS) and this is more likely to be where you would want to put your static content.
This article provides some insight into your options http://www.ibm.com/developerworks/websphere/techjournal/0211_brown/brown.html.