Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » EPF » Published Process Issues
Published Process Issues [message #30054] Fri, 16 February 2007 07:07 Go to next message
S.Saravanan is currently offline S.SaravananFriend
Messages: 40
Registered: July 2009
Member
1) The navigation path (Top of each screen) is created only for the
framework view. For rest of the standard category view or the custom
categories view, we are able to see the navigation path generated. How to
get this?

2) We created a discipline view and when the task page is opened from this
view for a discipline the information for a particular task say 'X' is
different of the same what we see in the Delivery process or the framework
view. But when we looked in detail, the delivery process shows the task as
task descriptor and the discipline views shows as TASKS. Information that
gets lost is ASSITED ROLES, EXTERNAL Inputs. But ideally in the published
output for a same task if I navigate through any view we should be landing
in the same task page.

3) Similarly when we don’t give step descriptions, we hope it's not
required to display the expand buttons. What happens now is, it publishes
with the expand and collapse buttons for each step and on expansion it
shows a line for empty descriptions.

4) There should be an option to change the table section heading
names,specific to the orgaisation. EX: Illustrations is some thing we dont
use in our organisation. But If I need to change, currently i need to open
every individual html page and do the changes. I am not sure if there is a
easy way to do it.

Report message to a moderator

Re: Published Process Issues [message #30483 is a reply to message #30054] Fri, 02 March 2007 02:48 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: phaumer.xxx.com

(2) A Task Descriptor is an occurrence of a Task in a process. The Task
itself is defined independent of a particular process. A Task's
relationships represent defaults for their occurrence in the process.
However, the descriptor has additional relationships that we felt only make
sense in a particular process context. For example, that an artifact is an
external input for a task descriptor (i.e. it is not produced by any other
task in the same process) is context specific. The default task just
defines the general inputs required in general to do the work. Only the
process can define if these inputs are provided by other tasks in the
process or made available through external sources.

(4) Currently there is no way to not publish information that was entered
into the forms. If a form field is empty it will not publish it, but if
content was provided, it will publish it. To remove fields you could modify
the XSL files in the code.

--


Thanks and best regards,
Peter Haumer.

____________________________________________________________ __

PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Sarav" <Saravanan.Sankar@cognizant.com> wrote in message
news:aa4e50931b6d578ef160d967747fcedf$1@www.eclipse.org...
> 1) The navigation path (Top of each screen) is created only for the
> framework view. For rest of the standard category view or the custom
> categories view, we are able to see the navigation path generated. How to
> get this?
>
> 2) We created a discipline view and when the task page is opened from this
> view for a discipline the information for a particular task say 'X' is
> different of the same what we see in the Delivery process or the framework
> view. But when we looked in detail, the delivery process shows the task as
> task descriptor and the discipline views shows as TASKS. Information that
> gets lost is ASSITED ROLES, EXTERNAL Inputs. But ideally in the published
> output for a same task if I navigate through any view we should be landing
> in the same task page.
>
> 3) Similarly when we don

Report message to a moderator

Re: Published Process Issues [message #30826 is a reply to message #30483] Thu, 15 March 2007 09:49 Go to previous message
S.Saravanan is currently offline S.SaravananFriend
Messages: 40
Registered: July 2009
Member
I would not agree completely with point 4 reply. It works only for Form
fields. But when we dont select the Check boxes for propoerties like
Optional/Multiple Occurence etc for Tasks....and publish the process, it
just publishes for all the tasks with a table with all these properties as
empty cells.

How will we disable this before publishing.

Report message to a moderator

Re: Published Process Issues [message #576741 is a reply to message #30054] Fri, 02 March 2007 02:48 Go to previous message
Peter Haumer is currently offline Peter HaumerFriend
Messages: 228
Registered: July 2009
Senior Member
(2) A Task Descriptor is an occurrence of a Task in a process. The Task
itself is defined independent of a particular process. A Task's
relationships represent defaults for their occurrence in the process.
However, the descriptor has additional relationships that we felt only make
sense in a particular process context. For example, that an artifact is an
external input for a task descriptor (i.e. it is not produced by any other
task in the same process) is context specific. The default task just
defines the general inputs required in general to do the work. Only the
process can define if these inputs are provided by other tasks in the
process or made available through external sources.

(4) Currently there is no way to not publish information that was entered
into the forms. If a form field is empty it will not publish it, but if
content was provided, it will publish it. To remove fields you could modify
the XSL files in the code.

--


Thanks and best regards,
Peter Haumer.

____________________________________________________________ __

PETER HAUMER
IBM | Eclipse Process Framework Committer
____________________________________________________________ __
"Sarav" <Saravanan.Sankar@cognizant.com> wrote in message
news:aa4e50931b6d578ef160d967747fcedf$1@www.eclipse.org...
> 1) The navigation path (Top of each screen) is created only for the
> framework view. For rest of the standard category view or the custom
> categories view, we are able to see the navigation path generated. How to
> get this?
>
> 2) We created a discipline view and when the task page is opened from this
> view for a discipline the information for a particular task say 'X' is
> different of the same what we see in the Delivery process or the framework
> view. But when we looked in detail, the delivery process shows the task as
> task descriptor and the discipline views shows as TASKS. Information that
> gets lost is ASSITED ROLES, EXTERNAL Inputs. But ideally in the published
> output for a same task if I navigate through any view we should be landing
> in the same task page.
>
> 3) Similarly when we don

Report message to a moderator

Re: Published Process Issues [message #577084 is a reply to message #30483] Thu, 15 March 2007 09:49 Go to previous message
S.Saravanan is currently offline S.SaravananFriend
Messages: 40
Registered: July 2009
Member
I would not agree completely with point 4 reply. It works only for Form
fields. But when we dont select the Check boxes for propoerties like
Optional/Multiple Occurence etc for Tasks....and publish the process, it
just publishes for all the tasks with a table with all these properties as
empty cells.

How will we disable this before publishing.

Report message to a moderator

Previous Topic:Can't get update manager to function correctly
Next Topic:Problems when exporting data (WBS, actors) from EPF composer
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 23:07:59 GMT 2024

Powered by FUDForum. Page generated in 0.03345 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly