Eclipse Community Forums: EPF » Creating new fields

Help

Home

Home » Archived » EPF » Creating new fields

Show: Today's Messages :: Show Polls :: Message Navigator

Creating new fields [message #48620]

Thu, 06 March 2008 21:22

Eclipse User

Originally posted by: stuart.macd.gmail.com

Can someone put me on to documentation that explains how I can do the
following:

1. Create an outputs 'updates' field for the task workproducts tab page

Taking it from being the current

mandatory inputs
optional inputs
outputs

to

mandatory inputs
optional inputs
outputs
updates

The updates field is essentially the same as the outputs field, but it
will allow an important distinction to whether the output work product
already exists elsewhere in the project.

I have tried to find this information, but I cannot find this kind of
customization help listed anywhere.

Any suggestions that you may have will be appreciated.
Stuart

Report message to a moderator

Re: Creating new fields [message #48774 is a reply to message #48620]

Tue, 25 March 2008 15:24

llauramelie

Messages: 28
Registered: July 2009

Junior Member

Hello everybody,

I'm really interesting in having an answer to that problem too. I hope
that CREATING NEW FIELDS under every content element would be possible in
the next release of EPFC (I'm really looking forward to getting it ^-^).

My purpose is :
- to generate a RASIC (Responsible/Approve/ Support/ Informed/ Consulted)
view for every of my processes
- to change the name of some fields such as : "BriefDescription" under
Role editor
- to add the fields "input criteria" and "exit criteria" under the
Description view of my processes.

Thanks a lot to all Eclipse support team.

Report message to a moderator

Re: Creating new fields / adaptability features [message #51572 is a reply to message #48774]

Thu, 26 June 2008 07:41

Gerhard Schneider

Messages: 24
Registered: July 2009

Junior Member

Hello to all,

yes, that's exactly the feature I'm looking for, too. During my work for a
customer it turned out that an adaptability like that is necessary to
reach the user's acceptance.
Sure, one can work around by using Rich-Text-Sections, but this conflicts
with the general look&feel of the GUI.

Another nice feature would be the adaptability of the default
"collapse/expand" section behaviour. There are sections that always shall
be expanded when opening a page, but there are other sections on the same
page that shall always be collapsed first and only expanded on user's
request. It depends on the type of element which sections to chooose for
the one or for the other behaviour.

Last feature: a complete content dump to any file format. It is currently
not very easy to get a complete overview of what is already in the model,
e.g., to discuss it on paper with a customer. It would be completely
sufficient, for the first step, to have the possibility for a batch print
out of the content of a complete plug-in, like it appears in the preview
pane.

Just some thoughts, in case you're running out of other features ;-)

Best regards,
Gerhard

Report message to a moderator