Timer Component

Hi,

We are currently using your plugin in an Appian environment and have encountered an issue after upgrading to Appian 26.3.

According to your documentation, the color property accepts the following values:

• ACCENT, SECONDARY, POSITIVE, NEGATIVE
• or any valid 3- or 6-digit hexadecimal color code (with '#' prefix)

In our previous version (25.4), we were successfully using hexadecimal color values without any issues. However, after upgrading to 26.3, the interface now throws a validation error indicating that only the named values (ACCENT, SECONDARY, POSITIVE, NEGATIVE) are allowed.

Appian Support has confirmed that this is not a platform limitation, as native components in 26.3 still support hexadecimal color values. Therefore, it seems this behavior is coming from the plugin itself.

Could you please confirm:

1. Whether this is a known issue
2. If there is an updated version of the plugin compatible with Appian 26.3
3. Or if there is any workaround to continue using hexadecimal color values

This is impacting our upcoming upgrade plans, so we would really appreciate your guidance.

Thanks in advance for your support.

Best regards,

Hi,

We are currently using your plugin in an Appian environment and have encountered an issue after upgrading to Appian 26.3.

According to your documentation, the color property accepts the following values:

• ACCENT, SECONDARY, POSITIVE, NEGATIVE
• or any valid 3- or 6-digit hexadecimal color code (with '#' prefix)

In our previous version (25.4), we were successfully using hexadecimal color values without any issues. However, after upgrading to 26.3, the interface now throws a validation error indicating that only the named values (ACCENT, SECONDARY, POSITIVE, NEGATIVE) are allowed.

Appian Support has confirmed that this is not a platform limitation, as native components in 26.3 still support hexadecimal color values. Therefore, it seems this behavior is coming from the plugin itself.

Could you please confirm:

1. Whether this is a known issue
2. If there is an updated version of the plugin compatible with Appian 26.3
3. Or if there is any workaround to continue using hexadecimal color values

This is impacting our upcoming upgrade plans, so we would really appreciate your guidance.

Thanks in advance for your support.

Best regards,

Hi,

Thanks for your response.

I actually share the same view, and that’s why the first thing I did was to open a support case with Appian. However, they have redirected me back to you, indicating that this is likely related to the plugin rather than a platform change.

From my perspective, it does look like something may have changed in Appian 26.3. My guess is that it could be related to the recent introduction of CSS branding capabilities, and that something in that change might be unintentionally enforcing stricter validation on color parameters.

At this point, it seems like we are in a gray area between platform behavior and plugin compatibility.

Please keep me posted on your findings, and let me know if you need any additional details or testing from our side.

Thanks again for looking into this.

Best regards,

Hi Alberto Cortés ,

We recently identified this issue through one of our internal teams using the component. Based on our initial analysis, the “color” validation is being enforced from the Appian side. As a result, the validation message appears over the interface—this typically happens when validation is handled by Appian—rather than displaying as red text beneath the component, which is the expected behavior when the component itself triggers validation.

Therefore, this does not appear to be an issue with the plugin. At this time, we believe it is a compatibility concern and do not yet have a definitive solution.

We will continue investigating and provide an update for the plugin. However, this may take some time, as our testing environment is currently on version 25.4.

Regards,

Praveen Santhosh.