I was asked to create a custom event in Policy Center. A GuideWire employee said that I should see the GuideWire docs. I searched the documents that I had and all I could find was how to add a new event for something in Billing Center. It seemed to suggest that I should add the new event to the type list. There doesn't seem to be a type list for the other types of events that I am monitoring, so that doesn't seem to be an option.
This should be as simple as calling
.addEvent("CustomeEvent")
on any entity object.
What you probably should read is the Messaging section of the Integration Guide in the documentation. This new event - whatever you call it - has to be mentioned in Messaging part of the configuration on the particular destination and then appropriately filtered/handled in Event Fired Rules.
Related
PROBLEM
We want to track changes in user calendars, but are concerned with how often we'd need to check 2000+ user calendars (Outlook).
Would the process of monitoring over 2000 user calendars present a problem for our network?
WORKFLOW
Trigger (Check for calendar change) -> ACTION (Http: update a DB)
The Trigger below checks a calendar every 2 seconds. Is there a trigger that behaves like a "subscription" object where it simply handles a change notification?
For the question about how often to check the calendar events, it depends on your requirement. In my opinion, if you set check event every 2 seconds(it's a little bit more frequent), you'd better check if your logic app set as run in parallel. You can click the ... button of the trigger and click "Settings". Then check if it is same to below screenshot.
For your question about is there a trigger that behaves like a "subscription". I'm afraid it doesn't exist a trigger which can implement this requirement in logic app. We can also check if any backend api can implement it, we can see the graph api document.
The example in above screenshot is for mailFolders, but it's same with events. We can see it is necessary to specify a user(like me) or a group before the /events. So I don't think we can monitor the subscription events. You can raise a post on Azure feedback page to suggest developer add this feature.
I developing a slackbot and have implemented events
just like a applied event on member joining channel
https://api.slack.com/events/member_joined_channel
I need an event when user is being removed from team
This kind of event currently does not exist. Check this list for an overview of all existing events.
Please contact the Slack team and suggest this event for a possible future implementation at feedback#slack.com.
Is there any option to subscribe users automatically to the asset publisher?
I saw this:
message.boards.subscribe.by.default=true
but, I need it for the asset publisher
Thank you!!
message.boards.subscribe.by.default subscribes a user to the message board thread they're answering to - e.g. after they interacted with the message board.
What would be the interaction with AssetPublisher that you're intending to trigger this automatic subscription? There's typically only the author(s) of an asset publisher adding articles, and they don't need to interact with AssetPublisher in order to make other articles appear because AssetPublisher only filters and shows whatever matches the current criteria.
This is a long way to say "no, there's no such property". However, there's Liferay's API, which you can use to codify the criteria for subscription. This will naturally be more effort than setting a property, but it's your only option.
I have a few events in my apps that have parameters For example
Ads - Custom Event
Network Name - event param
Status - event param
So the main event is Ads and I'm passing in the network name say "Admob" for example and the status so "Failed" for example.
Is it possible in flurry to see how many users who saw the "Admob" network also returned a status of "Failed"?
Yes there a couple of ways that you can calculate the number of user who triggered an event with a specific parameter value.
1) From https://dev.flurry.com open your project and visit Manage -> Segments. You can create a segment of users that have triggered an event with a specific parameter value.
2) You can use Flurry's Explorer tool to perform the calculation very quickly. See the green banner at the top of the developer portal or the 'Explorer' link from the project page.
Let's assume there are two domain entities:
UserImages with methods addNewImage(), removeImage($imageId), getImages($from, $count).
UserProfile with fields name, age, mainImageId, etc.
Following functionality is desired inside the domain: when application layer calls UserImages -> addNewImage(), UserProfile -> mainImageId is set automatically in case it was empty.
So, what is the best way and best place to implement an in-domain over-entity business logic? Domain events with observing services, referencing special services from the entities, or somewhat else?
I create all the entities using a some kind of factory, i.e.
$userImages = Domain::userImages($userId); // getting an instance of UserImages
$newImageId = $userImages -> addNewImage(); // adding a new image
I also should mention that I will have a lot of logic like described above in my project.
Thank you very much for help!
First off, as specified in your other question, UserImages is not itself an entity. Instead, there is likely an entity called UserImage which refers to a user's image, singular. A UserImageRepository can then provide access to all images associated with a user, using pagination where necessary.
Now, the use case is:
When a new user image is added, if a user's profile image is not set,
set it to the added image.
The term when indicates a domain event. In this case, the event is UserImageAdded. The bold if and the subsequent set represent the desired behavior in response to the event.
To implement this use case, an event must be published when a user image is added and a handler implementing the desired behavior must be subscribed to this event. This linked domain events article provides a sample implementation in C#, however the concept can be easily ported to PHP. Overall, the required components are:
An application service which handles the adding of user images. This service will publish the event.
A domain event publisher which is called by the application service and allows decoupling of publishers from subscribers.
A domain event handler which handles the UserImageAdded event and invokes the desired behavior.
User sounds like Aggregate for me (it's difficult to give you an opinion without context :) ), but it can solve your problem.
If Profil and Images are differents bounded context, may be you can use Domain events (it's helpful for cross bounded context communication)