Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
CCStd v6: Adding Source Diff and Viewing All Jobs
PaulD
In CCStd, v6:
Does anyone know if it is possible to add the "Source Diff" functionality to the filesys Action Menu?
Or is it possible to give the user the ability to see All their assigned workflow tasks?
i can't find anything on either of these topics.
tia
Paul
Find more posts tagged with
Comments
Adam Stoller
Taking the questions in the reverse order
- doesn't the Tasks portlet already have a My Tasks view that shows a list of all the current user's assigned tasks?
As for Source Diff functionality I imagine you can add it to the menu list like any other menu customization (have you looked at the UI customization guide?) - you might want to add it to both the top-level action menu that appears Work In Progress portlet as well as in the File Actions menu that appears in the Folders / Files view.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Bjorn
Find the global ID for Source Diff in the CCPro ref files and reference it in a new menu item in ui_custom.xml.
Example...
<action-list id="iw.ccstd.list_directory.file_list.actionlist">
<menu id="iw.ccstd.list_directory.file_actions.menu">
<iwov-insert-after id="iw.ccstd.list_directory.file_actions_visual_diff.link">
<link id="cust.ccstd.list_directory.file_actions_source_diff.link" refid="_iw.ccpro.source_diff.link" label="View Source Differences" />
</iwov-insert-after>
</menu>
</action-list>
PaulD
Yes, you are right and I got it to work. I
assumed
the ccpro links would not work with ccstd. Glad i was wrong and thx again.
Re my workflow question, the two default views offered are mutually exclusive. One shows all the user's current
individual
tasks and the other shows all the
group
tasks the user is associated with. I'm looking for a way to show both associations in
one
list. They basically want it the way it was. That may mean, of course, letting them use the legacy webdeskpro interface...
thx and stay tuned for more dumb questions.