Documentation Index

Fetch the complete documentation index at: https://help.idibilling.com/llms.txt

Use this file to discover all available pages before exploring further.

IDI version 26.8 is now available.  Click here for details: IDI Updates.

IDI Platform Version 24.7 Details

Prev Next

IDI Platform Version 24.7 Core Bulletin

Change Orders

Functional Area

AR/FR

Description

Orders Web Module – Web Sales

FR 3580

Credit evaluations on web transactions

This adds the ability to perform a credit evaluation on a web transaction initiated by a properly configured starting block.

Note:

This functionality supports automatically adding a deposit to a transaction per credit evaluation logic and requires starting blocks to be enabled.

Orders Web Module

FR 3580

Adding a manual deposit as a transaction line item

This adds the abiity to manually add a deposit as a line item on a transaction. This functionality is permission-based and is supported with or without starting blocks enabled.

Orders Web Module

FR 3580

Seamless navigation between Orders and Customer Care to create a new customer

This provides the ability to navigate directly to Customer Care from the Orders Enhanced Customer Search to create a new customer and then return to the transaction seamlessly. This functionality is supported with or without starting blocks enabled.

Paymentus/
Workflow Triggers

FR 3606

PaymentusTransactionCreatedTrigger

The PaymentusTransactionCreated trigger initiates an event each time a Paymentus transaction record is generated. This process occurs through Paymentus Notification Service (PNS) integration. This trigger lets you activate workflow actions whenever a record is made for a Paymentus transaction attempt.

Bulk Feature Import

AR 9343

Starting block ID in FeatureBulk Import

This adds Starting Block ID to the Bulk Data Feature Import as an optional integer. When included in a row, the specified starting block will start the order for that row.

Notes:

Resolved Known Issues

Functional Area

PR

Description

Orders

84673

Workflows notgenerated after transaction is submitted

Transaction processing is governed by workflows. The workflows were periodically not being created after a web transaction was submitted.

To mitigate this, the code was updated to wait for a response when queueing up a message to start the workflow. In cases where this queueing fails, an error is thrown.

Payment Processing – Paymentus

84681

Username missing from Paymentus Schedule Paymentspage

Payments sent to Paymentus did not include the user name.

The Schedule Payments page was updated to include the user name.

Payment Processing – Paymentus

84697

Installment plan payoff date reverted to the plan creation date

When processing an installment plan payoff, the payment posting date was reverting to the installment plan creation date. The processing was missing a step to filter out previously invoiced installment plan details. The step to filter out previously invoiced plan details has been added.

RateBill

84682

Issue with Group Services by Class of Service optional XMLreport

This issue is related to the XML optional report delivered by AR 9321 in CostGuard version 24.5. The report is meant to display service charges, taxes, and discounts for each service, grouped under their respective Class of Service on an invoice. In the initial implementation, the grouping was only looking at the class of service overrides and not the default class of service coming from the service’s product. This caused all services without a class of service override to be grouped under Other class of service rather than individual class of service. Service-level taxes subsequently were not being broken out by service.

The report now uses the service’s products to set class of service groups.

Communications

84355

Create new notification error

The Communications web mdoule Create New Message/Notification form (+New menu option) lets you send a new message or notification directly from the module to test it before using it in another application. When using this form to send a new notification, the form returned an error indicating the To field was not populated even though it was.

The form no longer returns this error if the To field is populated.

Customer Care

84659

Preview Invoice picks wrong bill period after bill cycle change

After a bill cycle change, generating preview invoices in Customer Care sometimes showed a bill period one month in advance if the account had not been billed in the new bill cycle.

This has been updated to handle bill cycle changes correctly.

Customer Care

84671

Edit options on send email were blacked out

When using Customer Care to send an email (Account > Communications page or Communications tab on the Account Summary page), the editing options for font, underline, and so on, were blacked out. This was due to an infrastructure maintenance change.

Styling updates were implemented to enable these editing options.

Treatment Workbook

84663

PerformanceImprovements

The process for evaluating if a customer’s status should change was taking too long.

Updates were made to improve the performance of these Treatment Workbook Account Order functions: hotline, suspend, disconnect, and restore.

Platform System Deployment Updates:

Module

Target Deployment Updates

Communications

07/09/2024