I need to capture the events for tagging in CQ. Need to capture the tags whenever the users add/remove/change/delete tags in CQ tagging console.
I have an idea to implement a workflow & launchers to handle the event handling in tagging console. Whenever such event occur, automatically the workflow will get trigger and get the events. I don’t know how to implement such workflow. Please share any url related to this.
Also I heard that JCR listener, Is this helpful to manage event handling?
Please share if you have come across any requirement ?
I would also use a workflow model with an appropriate launcher, as you suggested.
The launcher is actually quite easy to create - you can specifiy the location to watch (probably /etc/tags), the type of event (node creation, update, deletion) and the workflow to be triggered.
For workflow model creation, adobe has some articles here:
http://docs.adobe.com/docs/en/cq/5-6-1/workflows/create-models.html
Related
I'm trying to find whether the Episerver Scheduled job (Episerver CMS 11) is triggered manually or automatically.
While on finding in Episerver documents I do see the 'ScheduledJobTrigger' and 'ScheduledJobLogItem' are related to this. But still, I am unable to find out how to call the service for implementation and get the expected value. Can anyone help me on this?
In code, the ScheduledJob will not have a user associated with it's context when fired automatically (either via API or scheduled firing), whereas a manual start will have user context associated to it.
If you are looking to identify if this was triggered manually, checking that user context may be what you are looking for.
Let's say I've an event sourced blog engine application in which I can create, publish and un-publish posts... I'm now wondering how to implement the post deletion command. Should I create a post deletion event, store it in the event store, and then, listen to that event to remove the projection, or should I fully delete the post, including any related events from the event store? The problem with the second solution is that I wouldn't be able to rolling back the deletion and I'm pretty sure that removing events from the events store is a really bad practice with event sourced applications.
Thank you for your advise.
If you are in a domain where you are using event sourcing, presumably because there is business value in temporal queries, then you are probably going to want soft deletes, rather than actually destroying the history you have accumulated.
See also: Don't Delete -- Just Don't.
Whenever the user submits a workflow request from Enterprise portal clicking more than once, multiple instances are generated. Kindly suggest a way to avoid as it is misleading.
Thank you.
Have a look here
In the event this.WorkflowActionBar.EvaluatingCanSubmitToWorkflow you could via the EP's Business Connector session call a static method in X++ to check whether a workflow for your current process / document / whatever already exists and avoid submitting it again. How you determine that of course depends on your environment / process etc.
Is there an automated way to detect when a requirement's status is set to 'Approved'? The business need is to alert an external app each time a requirement is approved.
One option is to to build an add-in for Enterprise Architect. I wrote some articles about that subject that should help you get started.
In this add-in you can implement the "events" EA_ConContextItemChanged to capture the status before it was changed and EA_OnNotifyContextItemModified to compare it with the previously captured status.
It might be possible that you can also use workflow scripts, but I'm not sure (nobody really uses that).
In sharepoint 2010 I need to be able to set a review date on a document and be emailed when this review date is reached. Is this possible?
Thanks for any pointers
I would create a very simple Workflow for this. You could just fire up Sharepoint Designer, create a small Workflow which checks whether the document in question has been reviewed and otherwise send an e-mail or a task to some person.
Try out Sharepoint Designer & Workflows if you haven't done so. Reminders are a very easy thing to do.
This answer details a few different ways to do this - workflow, scheduled jobs, open source and commercial add-ons.
Dated reminders in sharepoint calendars
To make it the most robust solution, I would suggest to customize the Alerts framework of SharePoint. SharePoint allows following customizations (as documented here http://msdn.microsoft.com/en-us/library/bb802949.aspx)
Adding or removing buttons from the
alert e-mails.
Changing the cascading style sheet
used to format e-mail alerts. This is
particularly useful for sites that
want to create a consistent
appearance.
Changing the latency of "immediate"
alerts by adjusting the default timer
interval.
Override the templates used to create
e-mail or SMS alerts, either by
creating a new template or by setting
the SPList.AlertTemplate property.
Creating custom filters by using Collaborative Application Markup
Language (CAML) queries in the
element in the alert
templates.
Programmatically setting or changing
the mobile messaging service provider
(MSP) that forwards SMS alerts to
mobile telephones.
Adding custom event handlers that
respond when a user creates or
modifies an alert. Also, custom
handlers that respond to the alert
sending event can be created.
Programming the alerts framework by
using the SharePoint Foundation
object model. For more information
about how to customize alerts
programmatically, see SPAlert.
If your list supports sending alerts based on a View, you are lucky, A NO CODE SOLUTION is already there for you. You can create a View with filter condition like "DueDate is equal to [Today]" (and possibly "AssignedTo is equal to [Me]) and then subscribe to any changes to that view.
If you end up with custom alert filter, following links may get you started:
http://egrimmett.wordpress.com/2008/01/17/custom-alerts-part-2-filters/
Link