Webtop links auto published

Here's sort of how that goes:

1. The resource and its associated customization are created via Web GUI or some other way
2. The resource and customization are associated with the access policy
3. The access policy snapshot with that information is created (this is what happens when you do "apply access policy")
4. The resource and full webtop are assigned to the user's session by the access policy.
5. Full webtop shows up and loads the resources and their customization.

So, depending on your requirements you have a few options. Here are some important points:

1. You can't dynamically create resources at run-time because the objects must first exist in the snapshot.
2. You can customize the webtop's HTML and JS as much as you like using Advanced Customization.
3. You cannot dynamically execute server-side code in the full webtop because it's cached as a static file. You'll notice that there is some PHP in there, but that is only executed ONCE. Thereafter, it's cached.
4. You CAN include client-side javascript in the webtop.
5. The APM renderer (http server that sends pages to end-users) does do real-time substitution of session variables. For example, %{session.logon.last.username} becomes the user's username. You can use any built-in session variable or any you've created in this way.

So generally if I had to create a solution like this, I'd do some LDAP/AD queries and do some %{xxxxx} session variable substitution, then read that in with a clientside js function and render it in whatever way is appropriate. This would be complicated front-end web development, but not particularly abnormal.