Patch 10.3.2
This is a Minor Patch, it’s mostly for lazy third party data vendors and web forms posting policy data into TLD, refusing to use the Ingress API and refusing to actually provide any data so making us assume alot of it to make it work.
- Posting in a Policy with just a Product will auto-look up the Carrier ID and place it if just the Product ID is present.
- Posting in a Policy will now try to Figure out what Dates and Users you forgot to provide when posting it with a Status ID of 1( Active), 2, (Verified), 3(Converted)
- If you provide a negative status like posting in a Cancelled Policy you still need to provide Date Converted, Verified, Sold and Cancelled along with the status for it to be in the proper stage, otherwise it will be a Cancelled Status in Quote Stage.
- We may revise this later, the question is do we want to make more DB Calls and CPU Cycles when people just simply refuse to understand or present the appropriate data or not.
- If you provide a negative status like posting in a Cancelled Policy you still need to provide Date Converted, Verified, Sold and Cancelled along with the status for it to be in the proper stage, otherwise it will be a Cancelled Status in Quote Stage.
- Post System now supports Add Policy on Lead Dupe and Add Dependents on Lead Dupe outside of the Uploader and as Vendor Meta.
- This was again done to appease those not willing to use the Ingress API.
- Added a new Feature to Prevent Agents and Fronters from Filling out any Data in the “Policy Number” field
- Because telling Agents to not put other random information in this field sadly doesn’t work.
- Some Minor Updates to our TCR Implementations and some Maintenance for 10DLC Campaigns
- Fixed an issue with an extra record being shown when Streaming Egress API. Started Counter at 1…