If I'm adding task through Calendar module (Calendar -> ListView -> add Task) then me and other users can see it in SharedCalendar, BUT I can't see tasks added through Project -> Tasks -> add Task in my SharedCalendar view. So, this is my question.
Can I see tasks added from other modules in shared calendar?
(my vtiger is 6.0.0)
Related
I am using Activiti 1.9.03 and Alfresco 5.2.4 enterprise versions. I have a requirement where I have to maintain the version of the generated report document and also uploaded document (if user edits it). Right now After each user tasks, I am adding two Publish to Alfresco tasks. This is making the workflow diagram unreadable.
I want to know the following things.
Is there any other way to handle versioning in Activiti instead of pushing the content to the Alfresco?
How can I upload the content programatically using JAVA or Javascript task in a listener, so that I don't have to keep the Publish to Alfresco tasks in the workflow definition. OR
Is there any way to hide the Publish to Alfresco tasks on the workflow diagram?
Any help will be appreciated...
Thank you
In APS,There are Services like AlfrescoService,AlfrescoContentService.
You can autowire those services in your Listner and you can use REST Call.
How do I add code activies to my hosted workflows in WF4.5? I know that when I create a new workflow application in VS, then hit F6 to compile it, it shows up in the toolbox. But with out creating an assembly that one of my users would have to import, how do I create a toolbox [code] activity in WF4.5?
Here's an article that discusses loading custom activities into the toolbox on a rehosted WF4 application: http://msmvps.com/blogs/theproblemsolver/archive/2009/12/23/rehosting-the-workflow-designer-in-wf4.aspx
Where I can find example for workflow implementation? Actually we are not able to attach workflow definition to a Page or Component. We have created new Workflow definition for Page and Component when we open a page and go to Workflow tab it is showing "Approval Status: Undefined"
We recently upgraded from Tridion 5.3 to Tridion 2011 SP1, we have executed the step mentioned in Upgrade manual "Upgrading existing default Workflow Process
Definitions"
As per my understanding under workflow tab we should be able to select workflow definition to be followed by Page or Component
For Pages, Workflow Processes are attached to Structure Groups (you'll be able to select the Process Definition in the Workflow Tab of the Structure Group). When attached to a SG, any page that you create or edit in that SG will start the workflow for that item. Note that Structure Group's do not inherit this setting, so every SG you'll have to attach the process to.
For Components, Workflow Processes are attached to the Schema (you'll be able to select the Process Definition in the Workflow Tab of the Schema). When a Schema has a workflow, any Component that is created or edited using that schema will be put into a workflow.
Note that child Publications won't automatically have Components and Pages kick into workflow. For example, if your schemas with attached Process Definitions are at the 010 level, and your components are at the 020 level, you'll have to go to the Workflow Tab in the Publication properties of your 020 level and make sure to check "Enable Workflow Process Associations in Shared Schemas and Structure Groups".
Hope that helps!
I'm trying to publish a page during Workflow. There are two environment that we are publishing to during workflow process: one to test and one to live. During the first automatic activity we are publishing to test and during that process the Components on the Pages don't need to be approved. We got that to work.
However when we approve the Page and the Page is being published to live, we need to make sure that we only publish approved Components (i.e. major versions).
In my code I'm using the Page.Publish method, but with that I can't specify that it should only publish approved items.
The publish method accepts an argument called activateWorkflow. When set to True it publishes both approved and unapproved items; but when set to False it gets added to the queue and we get a success message, but nothing gets published.
Anyone have any ideas how I can fix this, using the publishing method and without manually checking?
Thanks.
I ran into a similar issue when going through Component Workflow and having to publish static pages (no dynamic component presentations).
When publishing to test, as you mentioned, simply do activateWorkflow=true. For your Live environment you need to kick off publishing after workflow completes. I've resolved the issue via the event system for this. Here an article that discusses this in more detail that may help you:
http://www.tridiondeveloper.com/autopublishing-on-workflow-finish
It is not clear where you are performing the activities, are you doing this from within your workflow activities in Visio?
Publishing will always only publish items that are either in the approved status for that target and items that have finished workflow (major versions).
All that said, I believethe reason you are getting empty PublishTransacctions is because you are calling the Publish() method on new items before you finish the page workflow activity (which means your new item is still in workflow, so the false value means there is nothing to publish which is not in workflow). Try calling FinishActivity() before the Publish() method is called.
Perhaps you could post your code from the final step so we can see exactly what you are doing.
I would like my users to be able to create and edit their own content. However, after they create new content, and after they edit it, I would like to have a way to accept those changes. Meanwhile, before changes are accepted, the previous version of the node will remain visible. Can this be accomplished with workbench, or is there another route I should take?
You can make the node content type unpublished by default from [admin/structure/types/manage/article] where "article" is the node content type...and then you can use "views" module to display all un published node... then you can manage the unpublished nodes and make theme published...
then
you can use rules module to make the node unpublish after its edited by the user
Take a look at the Maestro module. It is a way to implement workflows into your site.
From the project page:
The Maestro module is a workflow engine/solution that will facilitate
simple and complex business process automation. The first release of
this module will be for Drupal v7.
Maestro has a number of components that include the workflow engine
and the visual workflow editor. The workflow editor is used to define
the workflow, creating a workflow template. The workflow engine runs
in the backgound and executes the workflow tasks, testing the tasks
execution results and branch the workflow if required. The workflow
engine will run every x seconds and execute all tasks that are in the
queue which have not yet completed. Once they execute and return a
success status, the engine will archive them and step the workflow
forward. Both these components have been developed to support any
number of different task types. New task types can be developed and
added much like the Drupal CCK module can support new field types.
I have installed and configure the "Maestro" Module in Drupal Commons.
actually in Maestro Module every time we should Load the Workflow and it will go through step by step.
Like
Admin: Publishing Workflow Load
User1: Assigend to add new Content.
User2: Review Content
User3: Publish Content.
Here I want to Skip the Admin Step Is it possible? When user create new content type it is automatically go for review.