Custom Message on Appian LogIn Page

This is possible if you are ok to have a check box where the users requires to select as accepting the given terms of service(Custom Message).
There is an option under Admin Console -> Authentication -> Appian -> Terms of Service Agreement. If you select the Terms of service Agreement option, a paragraph field would appear where you can give your custom message but along with this the user always requires to select the default check box to login which means the user is accepted to the given terms of service(Custom Message) on selecting the check box.

Thank you santhoshs. =]
I have considered that too. But we don't want user to take an extra action of ticking the box, so let see if there is another solution on this~

We found the solution. The solution is to update the <APPIAN_HOME>\ear\suite.ear\web.war\portal\login.jsp by adding the <label> tag inside the <div class=”field_layout”> tag of the Password

like this: 

<div class="field_layout">
<div class="input_below">
<input placeholder="<fmt:message key="Password"/>" id="pw" name="pw" type="password" size="34" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
</div>
<label style='font-weight:normal'>* Please input your username in all lowercase characters</label>
</div>

 

Then I restart Appian to take effect.

Hi everyone, I would like to share that Appian Support just told us that customizing the login.jsp page is no longer possible in v18.3 and they have never encouraged us to make any changes to these files.

joanneh I assumed you are not on 18.3? We have added custom message on the login page for the version prior 18.3. But now it is no longer working.

When I did that it was on 18.2 indeed...
If they do not encourage that, could you ask them is there a better way to achieve that without using custom message? Coz users just don't want to take an extra action on ticking the box which is not neccessary (necessary to make custom msg works but definetly not in business sense for this simple reminder)

They said as per documentation, it doesn't mention anywhere that we are able to customize these files. However Appian does support sign-in page links which allow us to add custom links to the sign-in page (via admin console).

And gave me a reference to this link: docs.appian.com/.../Appian_Administration_Console.html

One thing that I would say, Appian don't always allow for customization. I think it's because they market themselves as a low code platform, so they limit what designers and developers can do in terms of customization. My opinion at least.

> Appian Support just told us that customizing the login.jsp page is no longer possible in v18.3

Can you provide any additional info on this? My environments rely on custom login.jsp pages and our support contact hasn't mentioned anything to this effect.

This was what they told us:

"I have just checked internally with my team and confirmed that we do not support any modifications made to the login.jsp files, as per our documentation it doesnt mention anywhere that we are able to customize these files. However we do support sign-in page links which allow you to add custom links to the sign-in page if this helps you in any way.

For more information:  "

I didn't think that it would have been possible to edit the login.jsp page. Appian doesn't give a lof of freedom to extend the platform beyond what they have given. They do restrict access to most of everything.

Will Teoh (willt)

May I know if you have already installed v18.3? I haven't so I am not sure about the latest feature......

When you said "We have added custom message on the login page for the version prior 18.3. But now it is no longer working." , do you mean the login.jsp does not exist anymore? or the file is being locked up and unable to modify?

The login page (eg: .../suite/portal/login.jsp) still there, but any modification to the login.jsp will no longer reflected in the page. My guess is ever since they moved to Apache-tomcat, these .jsp pages are now load in memory or in java .class files.

Yes. We have installed/upgraded our LAB environment from 18.1e to 18.3c for testing and POC purposes only. Upgrades on DEV/QA/PROD won't be happening until early next year.

The login page (eg: .../suite/portal/login.jsp) still there, but any modification to the login.jsp will no longer reflected in the page. My guess is ever since they moved to Apache-tomcat, these .jsp pages are now load in memory or in java .class files.

Yes. We have installed/upgraded our LAB environment from 18.1e to 18.3c for testing and POC purposes only. Upgrades on DEV/QA/PROD won't be happening until early next year.

FYI, apparently this might be fixed in an upcoming hotfix.

This is confusing. We are both getting different info from Appian Support. Can someone from Appian confirms this please??

We have verified and confirmation from Appian Support that this will be fixed in upcoming hotfix as described by Mike.

Thanks!