What is Keyable in Guidewire PolicyCenter?
Is it related to entities?
How can we create this Keyable enities in Guidewire PolicyCenter?
Keyable is a type of entity in GW. According to documentation:
A keyable entity that has an ID, but it is not editable. It is possible to delete entities of this type from the database. Guidewire recommends that you do not use this entity type. Use versionable instead.
When you create a new entity you can select type as you can see below.
Related
I am using microsoft LUIS in my application.
I am configuring the intents and entities. When I set up the intents I can select works and mark them as entities. These create simple entities.
Simple entities cannot have Canonical Form and Synonyms as far as I can see and I cannot use any list entities I create in the intents screen.
How do I set an entities to be a list and link them to intents?
To create/add non-simple entities you need to create them via the Entities view. This view is accessible by clicking on Entities in the Sidebar menu:
Documentation on Adding List Entities to LUIS App
For my custom service entities build using Service-builder I can use the identity-type in service.xml so that my custom entity's primary key generation is handled by the underlying databases.
Is there a way I can have Liferay's entities to also use database's auto-generation instead of using a custom Counter?
Note: Cross posted on Liferay forums.
When registering a plugin step with the registration tool, there is option for "Secondary Entity". What is a Secondary Entity, and in what scenario would a CRM developer can use this option?
Thanks
Secondary entity is used for SetRelated and RemoveRelated messages, otherwise it should be null.
Secondary entity is child is the related entity of primary entity. Secondary Entity should used only when you want to trigger plugin for an event requiring two entities like the "SetRelated" message.
Please have look here: Link
Tech Friends,
How to link address entity to new custom entity in MSCRM 2011? I want to do something similar to contact entity which has linked address entity having multiple fields.
The same I want to do for custom entity. Thanks in advance.
The CustomerAddress entity is, frustratingly, locked to further relationships. You will need to create another custom entity to use as Address and link that back to Contact and Account (and hide the built in entity).
I'm developing a liferay portlet. I use Service Builder. The question is that do I have to use companyID and groupID in my entity fields? What should I do if I don't want to have these fields? If I don't use them how can I use resourceLocalService.addResources() method?
They are not required but they are convenient to have.
Liferay has many additional services available to you to use like permissions, users, document library. These services are almost always scoped to a portal instance, for example, Users are scoped to an instance which is tracked by companyId. Some are scoped to a group like document library.
So depending on what Liferay services you are planning to use and at what scope those services operate, it is convenient to have those values stored as well for easy lookup when you're calling those services you are using.
Notice that the DBA team didn’t specify these two foreign key fields in the tables, but you add them anyway. You do this because the DBAs didn’t know the internal workings of Liferay when they designed the table.
These fields are internal to Liferay and are used for context purposes in non-instanceable portlets.
CompanyId corresponds to the portal instance to which the user has navigated, and groupId corresponds to the community or organization to which the user has navigated.
Because you’ll use these field values as parameters in all your queries, the portlet will have different data in different portals, communities, and organizations.