Help with signature field in IXP unstructured model

Hello everyone,

We are using an IXP Unstructured model where we need to detect whether a signature is present or not.

I added a boolean “Signature” field in IXP and trained the model with a sufficient number of documents.

However, when I run the process and push the document to Action Center, the signature field is not auto-extracted. Instead, the user is always prompted to manually select Yes/No. All other fields are working as expected and are auto-extracted with minimal human-in-the-loop involvement.

What am I missing here? My goal is to have the signature automatically detected without user intervention.

Any guidance would be appreciated.

image

Hi @tejaskumar.darji

I think boolean fields are not supported for auto-extraction and are always prompted for manual input in Action Center. To detect a signature automatically, use a Text field and derive the Boolean value in the workflow based on whether extraction returned a value. I’m not much sure but you can try.

Happy automation with UiPath

But when I push the document to IXP in training it automatically populates the value True/False based on signature. I’m wondering why it works in training and not in action center.

@tejaskumar.darji

Try to refine the prompt..I see a positive statement followed by a negative one, which might reduce the confidence. Mention exactly what is needed and typically if there is any specific position or beside some field try to mention them

in unstructured no training would help..only prompt needs to be changed

try to follow the instructions here

cheers

1 Like

Hello @Anil_G Thanks for your response on refining the prompt. However, the issue is not related to prompt refinement.

The Boolean Signature field is not being auto-extracted in Action Center. The same prompt works correctly when I manually push the document to IXP, but fails to extract the Boolean Signature field when processed through Action Center.

Please let me know if any additional details or logs are needed to troubleshoot this behavior.

@tejaskumar.darji

Is it the same doc that you are using in both places? also what is the confidence score you are getting

As per the best practices in prompt shared as well, I dont see many followed. Better check them as well

cheers

@tejaskumar.darji
In training, the Yes/No value is manually labeled and sometimes auto-retained to speed up annotation, but it is not a model prediction. At runtime, Boolean fields are treated as confirmation fields, so they are never auto-populated and always require user input in Action Center. This difference is by design.

1 Like

Thanks for prompt response. Just to clarify, are you suggesting that updating the prompt to a better version would fix the issue of auto-extraction of signature field in action center?

1 Like

@tejaskumar.darji

Yes that can help. With unstructured if something is not extracted training or reindicating would not help. Modify the prompt and making it clear helps

cheers

1 Like

Thanks @prashant1603765 but here the document says, signature can be used as Boolean. link - IXP - Best practices

@everyone I could not find any official documentation stating that all Boolean fields must be manually entered by the user in Action Center. If that were the case, every document would require user review, effectively making the process permanently human-in-the-loop.

Something is strange here! Need some expert guidance and insights from UiPath side on this item.

@prashant1603765 @tejaskumar.darji

there is nothing like boolean needs to be populated manually . Thats a wrong presumption

cheers

1 Like

Hello @Anil_G I updated prompt as per the best practice guideline that you suggested but still, I’m noticing same behaviour. Could you show me how you have configured signature at your end? I’m wondering how it is working for you.

For me it is always going to manual verification in Action Center.

Hi @tejaskumar.darji

IXP won’t auto-detect a signature just from a Boolean field. A Boolean needs to be derived from something. You have to train a visible signature/region field (the handwritten area). Once that is detected, you can mark the Boolean as Yes/No based on its presence. If you only use a Boolean, Action Center will always ask the user.

Hello @Monali_Vekariya As I mentioned in the earlier thread, the model is already trained on the signature boolean field and is auto-extracting it within the IXP window. The issue is that it is not auto-populating in the Action Center. We have already trained more than enough documents. Yes/No based on signature presence is already completed.

I think the issue is simple a Boolean field by itself isn’t considered “auto-extracted” in Action Center. Make sure the signature is detected as a region/handwritten field, and the Boolean is derived from that. Otherwise, Action Center will always ask the user to choose Yes/No.

Please check the trail thread where official document and link is provided suggesting for a Boolean field.

@tejaskumar.darji

It is extracted and coming as true as well



cheers

Hello @Anil_G thank you. Which IXP project model are you using? I’m using unstructured model. For me it only shows True/False inside IXP, and when I push it to Action Center it shows a Checkbox and asking user to enter value.

image

Any idea why it is showing different behaviour in my case. I’m using studio, I see you are using web studio version.

@tejaskumar.darji

Even I am using unstructured only

are you getting the field inside table only?

also did you customize anything for action center?

to verify can you try printing the valu..may be it is coming as true but action center is not able to identify the value

cheers