Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

LC workbench username and password

Avatar

Former Community Member

Hi All,

I just took over the LC project at my work and the pervious employee left abruptly. So there's not much documentation for me to follow for using the workbench. My question is:

- Where is the LC workbench user account located or how is it setup?

I am able to login into the websphere console, LC admin console, and LC form manager. 

I was thinking the login for the LC form manager should work for the workbench but when I try it the login failed to connect to the server.

Also I'm in a test environment and we are using https but our cert is not valid. This is not effecting the login to the websphere console or LC admin console. So I don't think this would effect the workbench login.

Any help is greatly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I was able to fix my problem so I'm going to share it for incase someone else have the same issue.

Our prod environment is LC ES4 and dev environment is AEM. This is b/c we were working on upgrading to AEM. To connect to the server on our dev we need to switch to the new AEM forms workbench. I was trying to use the LC Workbench which didn't work.

happy programming.

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

I was able to fix my problem so I'm going to share it for incase someone else have the same issue.

Our prod environment is LC ES4 and dev environment is AEM. This is b/c we were working on upgrading to AEM. To connect to the server on our dev we need to switch to the new AEM forms workbench. I was trying to use the LC Workbench which didn't work.

happy programming.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----