This content applies solely to Connected Claims, which must be purchased separately from the Appian base platform. This content was written for Appian 24.2 and may not reflect the interfaces or functionality of other Appian versions. |
IntroductionCopy link to clipboard
This reference page is designed to provide you with a comprehensive overview of the objects that require modification to work in your target environment. It lists each object and the specific values you need to adjust for optimal performance of Connected Claims.
There are two approaches for this:
- Direct Modification: Directly change the values to match your target environment specifications.
- Package Redeployment: Identify the necessary values, then redeploy the package with these values set in the configuration file.
IntegrationsCopy link to clipboard
Integrations | Note |
---|---|
FAI_getFraudScore | Holds Username and Password of Neo4j. Leave unconfigured if you don't want to set up the fraud systems integration. |
FAI_relatedEntities | Holds Username and Password of Neo4j. Leave unconfigured if you don't want to set up the fraud systems integration. |
ConstantsCopy link to clipboard
Environment and service URLsCopy link to clipboard
Constant | Value/Get Value |
---|---|
CCS_SITE_URL_FOR_ SAFE_LINK |
Environment URL for Customer Service. Format: https://xyz.appiancloud.com/suite/ |
CCS_SWITCH_WRITE_ TO_NEO4J |
FALSE Note: This constant is for integrating the fraud graph. If you do not have the fraud graph on the target environment set up, then set the value of constant = FALSE. |
CF_ENVIRONMENT_URL | CF Site URL Format: https://xyz.appiancloud.com/suite/ |
FSA_SITE_SAFE_URLs | Holds the safe URLs for various tabs in Field Service Applications. Format: 1. https://xyz.appiancloud.com/suite/sites/field-service-app/page/work-orders 2. https://xyz.appiancloud.com/suite/sites/field-service-app/page/inventory 3. https://xyz.appiancloud.com/suite/sites/field-service-app/page/customer-360 4. https://xyz.appiancloud.com/suite/sites/field-service-app/page/services |
FSA_SITE_URL | FSA Site URL for Start Process Format: https://xyz.appiancloud.com/suite/tempo/start-process/ |
ICM_BASE_URL | Base Environment URL. Format: https://xyz.appiancloud.com/suite/sites/ |
ICM_FNOL_SITE_URL | FNOL Site URL. Format: https://xyz.appiancloud.com/suite/sites/insurance-first-notification-of-loss |
ICM_FAI_SITE_URL | FAI Site URL. Format: https://xyz.appiancloud.com/suite/sites/insurance-fraud-alerts-and-investigation |
ICM_SUBROGATION_SITE_ URL |
Claim Recovery Site URL. Format: https://xyz.appiancloud.com/suite/sites/claim-recovery |
ICM_SETTLEMENT_SITE_URL | Settlement Site URL. Format: https://xyz.appiancloud.com/suite/sites/insurance-claims-operations-settlement |
ICM_FSA_SITE_URL | Insurance FSA Site URL. Format: https://xyz.appiancloud.com/suite/sites/field-service-for-insurance |
ICM_CSA_SITE_URL | Insurance Litigation Site URL. Format: https://xyz.appiancloud.com/suite/sites/insurance-customer-service |
ICM_LITIGATION_SITE_ URL |
Litigation Site URL. Format: https://xyz.appiancloud.com/suite/sites/insurance-litigation-cases |
ICM_PROCESS_MINING_SITE_ URL |
Process Mining Site URL. Format: https://xyz.appiancloud.com/suite/sites/Process-Monitoring-and-Improvements |
SERVICE_360ENVIRONMENT URL |
Base Environment URL Format: https://xyz.appiancloud.com/suite/ |
Business rulesCopy link to clipboard
Constant | Value/Get Value |
---|---|
BREM_CATEGORY_ID_CLAIM_ROUTING_ PRELIMINARY_RISK_ASSESSMENT |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_AML_ BENEFICIARY_VERIFICATION |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_CLAIM_ COMPLEXITY_CLASSIFICATION |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_CLAIM_ ASSIGNMENT |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_CLAIM_ EXPENSE_INTITIAL_RESERVES |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_CLAIM_ LOSS_INTITIAL_RESERVES |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_CLAIM_ AUTO_SETTLEMENT |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_REJECT_ APPROVE_CLAIM_AFTER_FNOL |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_FNOL_ VALIDATION |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_CATEGORY_ID_INITIATE_ SUBROGATION |
Update/ Verify the value of this constant to the ID of the business rule created. If you create this category from the front-end business rule configurations, the ID can be found by triggering this query. SELECT RULE_CATEGORY_ID_PK FROM \`BREM_RULE_CATEGORY\` WHERE \`RULE_CATEGORY_NAME\` LIKE '%<Name of rule category you provided on front end>%' |
BREM_INT_ATTRIBUTE_ EXPRESSION |
Set the value of this constant with the ID returned by this query: SELECT \`RULE_ATTRIBUTE_ID_PK\` FROM \`BREM_RULE_ATTRIBUTE\` WHERE \`RULE_ATTRIBUTE_NAME\` LIKE '%DummyExpressionResultAttribute%' ORDER BY \`RULE_ATTRIBUTE_ID_PK\` DESC |
Data sourcesCopy link to clipboard
Constant | Value/Get Value |
---|---|
BAM_DATA_SOURCE | jdbc/Appian (BAM framework Datasource) |
BFM_DATA_SOURCE | jdbc/Appian (BFM framework Datasource) |
BREM_DATA_SOURCE | jdbc/Appian (BREM framework Datasource) |
CCS_DATA_SOURCE | jdbc/Appian (CCS framework Datasource) |
SERVICE_360_DATA_SOURCE | jdbc/Appian |
QST_TXT_DATA_SOURCE | jdbc/Appian |
Email and Service 360Copy link to clipboard
Constant | Value/Get Value |
---|---|
CF_SURVEY_SENDING_EMAILS | Sender email to be used to send email. |
SERVICE_360_COMMS_EMAIL _SENDER_SENDGRID |
Sender email to be used to send email for support. |
SERVICE_360_SENDER_EMAIL | SELECT `email` FROM `CRM_CONTACT` WHERE `email` LIKE '%processmodeluuid%' and `lastname` = 'Intake' and `firstname` = 'CLAIMS' Note: The value has to be appended by the environment URL in the end Format: processmodeluuid0006e543-b132-8000-01f5-7f0000014e7a@xyz.appiancloud.com |
SERVICE_360_ENV_CUSTOMER _RESPONSE_TEMPLATE_ID |
Create the template with the name 'Response from Customer' from the front-end configuration that you would like to use for this use case (i.e., wherein the email you expect as a user of this system to receive when a customer replies back on any existing email communication) |
SERVICE_360_SYSTEM_CONTACT_ID | SELECT `id` FROM `CRM_CONTACT` WHERE `email` LIKE '%processmodeluuid%' and `lastname` = 'Intake' and `firstname` = 'CLAIMS' |
SERVICE_360_ENV_CLAIM_APPROVED _TEMPLATE_ID |
SELECT `TEMPLATE_ID_PK` FROM `SERVICE_360_TEMPLATE` WHERE `TEMPLATE_SUBJECT` like '%Claim Approved%' Note: Create the template with the name 'Claim Approved' from the front-end configuration that you would like to use for this use case. |
SERVICE_360_ENV_CLAIM_REJECTED _TEMPLATE_ID |
SELECT `TEMPLATE_ID_PK` FROM `SERVICE_360_TEMPLATE` WHERE `TEMPLATE_SUBJECT` like '%Claim Rejected%' Note: Create the template with the name 'Claim Rejected' from the front-end configuration that you would like to use for this use case. |
SERVICE_360_APPIAN_CURRENT_VERSION | Appian version on which the target environment is running. |
MiscellaneousCopy link to clipboard
Constant | Value/Get Value |
---|---|
GOOGLE_MAPS_API_KEY | Holds Google Maps API key. This is used to have the smart address picker populated, as well as showing addresses on Google Maps in different apps of Connected Claims. |
ICM_FAI_USE_FRAUD_INTEGRATION | FALSE Note: If you want to have the fraud graph on your claim dashboard and don't have the fraud system (like neo4j), you can set the value of this constant as FALSE, which allows the system to render fraud graphs from the primary database. (This feature is only available for P&C - Automobile LoB until this Connected Claims version) |
FeedbackCopy link to clipboard
Was this page helpful?