We would like to modify the installement plan on customer invoice after that the invoice has been created (modifi it on the customer order is not possible due to multiple constraints)
We would like to be able to populate the installement plan information based on data on a custom entity.
We are having difficulties doing that with BPA Workflow
The isntallment information section is a bit touchy cause we must add/modify lines before registering other wise the register will not be possible.
When opening the Installmeent plan and discounts page : the batch request create the objkey
The InstallmentPlanAndDiscVirtualSet generate the OBJKEY
Any idea on how to populate the instalement plan lines using workflow please?
Thank you in advance
Page 1 / 1
Hi,
Any idea on how you want to populate the InstallmentPlanAndDiscVirtualSet ?
you could technically set a projection action on the create/update action and get the objkey into the workflow to do edits to the virtual set
you can invoke the api call directly inside the workflow too
thank you @kamnlk
the invoice is already present and wont be edited by going to the page.
once a month, based on works needs, a custom table will populate with the invoice_id and customer _id and the different installement plan that should be added.
the worklfow will be triggerd elsewhere and will go to the invoice and modifie the installment plan.
we think that the InstallmentPlanAndDiscVirtualSet will initiated by the default data already present
But when calling PopulateInvoiceData in the workflow we got error
@kamnlk do you think there is another way to do that pelase?
But when calling PopulateInvoiceData in the workflow we got error
@IFSRUNINNOVAL what is the error you are getting when invoked from workflow ?
@kamnlk we are getting the following :
@IFSRUNINNOVAL
I was unable to recreate the same error message, can you share the workflow triggering configuration (event/projection action) used when triggering the workflow?
what is the ifs version you are using?
@kamnlk we are triggering the workflow using debug mode to test the workflow as we advance.
we are using ifs23.1.13
@IFSRUNINNOVAL I was also able to recreate the issue with the workflow provided. This looks like a bit of a strange behavior. If possible, I suggest raising a support ticket to IFS to further investigate.
