Hi, 
You may use IFS Standard Documentation Approval process for this purpose, if you are looking to a introduce a further control over this process.

However, if you are looking forward such a functionality for meeting a legal requirement of a customer ( specially including such approver details in files for meeting a banking requirement ), better you report it as a new request to R&D.

Best regards,

Chirantha.

@BRSA Did you manage to do this? We need to implement something similar into our system and I am not sure the best way to implement?

Want all Supplier Bank Detail Creations and Amendments to have to be approved before the change is committed.

Thanks, 

Hi.

No, we have not found a proper solution yet. We have set up an event, sending emails when changes are made, but it is not a fantastic and valid solution. We will look in to the Documentation Approval process functionality, but it looks to be a complicated setup. IFS should look in to this problem, as it is a general requirement, to have an approval process. 

Brian

Hi 

There is no standard process for this.

That said you can use custom events to handle it. One user creates or amends the record, on saving the record, the custom event sets the blocked for use flag, thereby ensuring the new details cannot be used until approved. 

Second user goes in as the approver to unset the blocked flag which together with the use of custom fields allows for the recording of who did what for audit purposes.

Correct permissions obviously required.

Hi Neill

Thanks for you reply.

I hope IFS will make a standard solution for this, as it is a normal requirement in most companies?

I do not fully understand you suggestion concerning the custom event?

The “Blocked for use” flag can be manually changed. So, your suggestion is that the first user doesn't have permissions to change the “Blocked for use” bottom?

Only the second user have this right?  

If so, It is not a fantastic solution, as most companies just want to ensure that at least two people have approved the change! Have you got other ideas?

Regards Brian

We normally do this bank account approval using DocMan approval process and then use custom events to control the validations (New and Modify). For an example, when an existing bank account is modified, we have to make sure that No payment will be made to this supplier before approving the account details. We generally use Blocked for Payment check box for this validation and it is automatically triggered when electronic payment address is inserted or modified. Once the approval is process is completed,  the Blocked for Payment check box will be unchecked through an event.

Hi Eranda

Thanks for your reply. It sounds like a usable solution. However, there is quit some specification and setup to do, for it to work. 

Can you help us by sharing some more details of the events and solution you made? 

Regards Brian

Look like this is something IFS need to address in a more simple format -

I too am looking for a way to record auditable changes to the Supplier Bank Account details - I want to record - Employee, when the change was actioned, and what it was and what it was changed to.  I do not want to use Document Management - that is a Sledge Hammer to crack a nut - we really need to be able to set up auditable fields and somehow use this screen to record changes.  I also do not want to create a Spec and Custom Events to do this.

This should be bread and butter the IFS RnD.   Must be some good IFS Consultants on here that can take this back to the business - or tell me this is fixed in Cloud . 

For logging the changes on a field history logging can be setup for the information to be logged.

I would recommend  to log only basic data changes not transactional data.