Skip to main content
Solved

A Default Value cannot be set to an Enumeration using BPE

  • August 22, 2024
  • 5 replies
  • 204 views

Sudara
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Do Gooder (Partner)
  • 13 replies

Hi All,

We have noticed that setting a default value using a BPE workflow to a field that gets its values from a fixed database enumeration, is not possible as it gives an error. 

 

Ex: Automatic Payment Authorization field in Supplier → Invoice → General tab.

 

 

We have already tried the solution from the post Set default value for a list using BPA | IFS Community but we still keep getting this error. 

 

Is this a bug in the standard application or are we missing something? Help!

 

TIA

Best answer by SimonTestard

Trying to replicate what you’re doing with Automatic Payment Flag, this seems to work just fine ?

 

Here’s an example:

 

No need to Register Process Enrichment Variables as AutomaticPayAuthFlag is already registered through the Default Method

 

Whenever you click , it properly fetches the Automatic Pay Flag to the appropriate value:

 

 

 

Just keep in mind you must record the variable as written in the enumeration, not the DESCRIPTION of the enumeration (so you record it as “AtFinalPosting”, not “At Final Posting”)

View original
Did this topic help you find an answer to your question?

5 replies

Forum|alt.badge.img+11
  • Hero (Customer)
  • 243 replies
  • August 22, 2024

What error do you get ?

 

Also can you share your BPMN Model.


Forum|alt.badge.img+11
  • Hero (Customer)
  • 243 replies
  • Answer
  • August 22, 2024

Trying to replicate what you’re doing with Automatic Payment Flag, this seems to work just fine ?

 

Here’s an example:

 

No need to Register Process Enrichment Variables as AutomaticPayAuthFlag is already registered through the Default Method

 

Whenever you click , it properly fetches the Automatic Pay Flag to the appropriate value:

 

 

 

Just keep in mind you must record the variable as written in the enumeration, not the DESCRIPTION of the enumeration (so you record it as “AtFinalPosting”, not “At Final Posting”)


Sudara
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 13 replies
  • August 23, 2024

Thanks so much for looking into this @SimonTestard! We will try the above and let you know. 

Btw, the error received was, 

IFS Web Version: 23.2.4.20240306160416.0

Date: 2024-08-22T23:08:56.912Z

 

---------------------------------------------------------------------------

 

Supplier/Invoice (server error)

Error while serializing contents.

 

This error happens when the server cannot serialize the data to be sent to the client.

A common cause is that one attribute's length exceeds the defined maxlength in the projection.

To find more info, open Log Window or Debug Console, refresh and then check Network Tab in DevTools. In the response there can be more detailed information about the exception.

Error details: N/A

 

Unfortunately, it looks like I cannot attach the model file here. Tried drag and drop and also the attach option. I think it's due to the file type.


Sudara
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 13 replies
  • August 23, 2024

@SimonTestard My colleague just confirmed that he was able to get it to work by removing a step as you had suggested.

No need to Register Process Enrichment Variables as AutomaticPayAuthFlag is already registered through the Default Method"

 

Thank you so very much!


Forum|alt.badge.img+1
  • Do Gooder (Employee)
  • 1 reply
  • November 6, 2024

Hi @Sudara ,

 

What is the reason for this error? 

The overwrite is done using the same value with the same variable name, why does the size of the request getting bigger and generating size error?

 

This error happens when the server cannot serialize the data to be sent to the client.

A common cause is that one attribute's length exceeds the defined maxlength in the projection.”


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings