Community Forum

Hi, Where can I find some documentation on the 'payment_succeeded' event being raised after a successful payment is made? I ask because we have for example 'external_reference' coded and in production as the field to expect holding this value, but examples on test is reflecting 'external_ref' as the field name.

Hi, After adding a beneficiary to a policy, a payload is sent to our webhook with ```json json "event": { "type": "policy_altered" } ``` According to the documentation 'policy_altered' isn't an event that is produced by the system, and its also not an event that can be subscribed to (this fails). Is 'policy_altered' a bug, and if yes, please can this be updated to the correct event type?

Hi, Is there documentation about the bank details that can be added to a beneficiary? Thanks

Hi there, We need to trigger a custom notification when an external payment method is added to a policy. From the documentation I cannot see if there is a lifecycle hook for payment methods added. I do see there is an event `payment_method_added_event`. Is it possible to hook into this event in the in the Product module code?

I've defined a component like this: ``` { "type": "number", "key": "alternative_mobile_number", "outputPath": "alternative_mobile_number", "label": "Alternative mobile number 2*", "validators": [ { "validation": { "min": 609999999, "type": "greaterThanNumber" } }, { "validation": { "max": 860000000, "type": "lessThanNumber" } } ], "props": { "prefix": "0", "colWidth": 6 } }, ``` When entering a 0 as the first digit I get redirected to a error page immediately:  Thanks. FYI: This was an attempt to build a cellphone number validation. As per my other forum post, support for that would help a lot.

Is it possible to set a custom message for a validator on a component? Something like: \` { "key": "some_field", "type": "text", "label": "Some Field", "validators": [ { "validation": { "type": "required", "message": "Please enter this value as it is of utmost importance!!!" } } ] } \` If yes, is there documentation for this? Joi validation when the whole page is submitted is a bit clunky for large pages. Thanks

Hi, I see from older release notes (<https://docs.rootplatform.com/changelog/root-release-update-january-2022#google-places-autocomplete-for-address-input>) and on the roadmap (<https://portal.productboard.com/root-platform/1-product-roadmap/c/33-google-places-autocomplete-for-capturing-addresses>) the Root supports capturing an address using google integration. 1. Can we get a demo of how this works potentially? 2. What are the costs involved to enable and run this feature? 3. Is there any documentation available for this feature? Thanks

Hi, I'm trying to add a cellphone-style input to the application workflow schema but the available validation and component types don't seem to allow for a component that ends up looking like the ones we see on the policyholder page. See below from the policyholder page:  Please advise how we'd go about adding this. There isn't a component like this documented on the schema component reference docs (<https://docs.rootplatform.com/docs/schema-component-reference#input-components>). Thanks

Good day We see example payment responses where there is a field called `finalized_at`. The create-async and update-async payment apis make no mention of this field. How would we specify this field?

After pushing version 90.5 to the OneSpark organisation (id d00e0ea4-0ee2-4c08-804d-61df85ca32ec) at 08:47:22 on Oct 31, I created policy number 899D385451 (id 4860bc3f-690f-400d-abb1-7cf7f72bb3ec) around 08:52:19 on Oct 31. I then proceeded to allocate an EFT payment for the policy a few minutes later from the policy details screen (https://app.root.co.za/orgs/d00e0ea4-0ee2-4c08-804d-61df85ca32ec/insurance/policies/4860bc3f-690f-400d-abb1-7cf7f72bb3ec) and then proceeded to cancel the policy. My expected result was that no refund would be allocated since the version pushed contains config which indicates the following: ` "coolingOffPeriod": { "applyTo": { "theFullPolicy": null } }, ` A refund was erroneously created. This is now the 3rd time I've ran this test and each time I end up getting the same result. I'm changing only the .root-config.json file and pushing from local doing `rp push --force`. Is that sufficient in testing this? (This is the way we test all changes before pushing to the dev branch)