User Profile & Activity

Product Support Moderator
Page
of 22
Posted: March 2, 2018 5:46 AM
Hello Eric,

Thank you for checking out. As announced in our blog sometime ago, the community forum is no longer an official way to obtain support as it's intended for peer developer discussion. Instead, active subscribers should reach out to us through Live Messenger with logged-in state.

With regards to updates, we continuously release product updates that fix stopper issues and certainly browser support enhancement. You should be able to see latest updates from Update Manager application that come with the software installation.

Our WebUI lineup is pretty much mature and solid in terms of both stability and features. While we're committed to provide regular updates to the lineup, we're also working on major features that target longer term. So far, we have several thousands commits of unreleased new features and counting. We'll publish a major release when we see fit.

I highly suggest you to continue renewing your subscriptions to avoid lapsed support and product updates. Feel free to reach out to us should you have further questions.

Hope this helps!
Posted: October 5, 2017 4:46 PM
Hello Nicolas,

This issue appears because you have ASPX markup while loading the tables programmatically from server. During postback, the ASPX markup overrides the last setting, thus the issue.

To fix the issue, simply remove the entire RootTable definition from your ASPX markup, and everything should work fine.

Hope this helps.
Posted: April 3, 2017 6:05 AM

Hi James,

Thanks for reporting this issue to us. We've identified the cause of the issue and will pubish a hotfix shortly.

Posted: October 19, 2016 3:32 PM

Dear Loren,

Thank you for your feedback. We haven't consider the fix for Chrome in iOS 10 at the moment. We'll check it out shortly.

Cheers,

Posted: September 24, 2016 12:57 PM

Hello Loren,

Thank you for your patience. We have resolved the issue in our WebUI nightly build 976.

Please find the attachment below for the hotfix.

Hope this helps,

Hi Jimmy,

The usage in the client can be found in the AppFramework which source code is publicly available. You can look deeper into the User.Infrastructure\UserService.cs which show the current implementation that works out-of-the-box in Crosslight. Feel free to extend the class, override the members as necessary to suit your needs, and register it through the dependency container.

With regards to the documentation, the key concept and class members for user management can be found here, although the page doesn't provide a guided-walkthrough on extending the class. As you may have aware, our team has added numerous walkthrough-style guides over the past months which you can find in both our blog and Developer Center. We'll keep hearing feedback from our customers and write guides based on the highly requested/asked topics.

Back to the original topic, if your application only use the Login or Logout method of the service, it should be safeto simply remove the methods in the server-side, and leave the implementation in AppFramework as is (considering they're not used).

Please let us know if you have any specific questions regarding the extensibility.

Hope this helps,

Hi Jimmy,

The methods in IdentityController are basically needed if they are consumed in the client, which is the case if the business template is purely used. However, if you've modified the client to certain extent, and you can ensure thatthe server methods are no longer consumed in the client, then it's safe to remove the methods in IdentityController.

When using custom tables, you're free to modify the IdentityController to suit your business requirements. For instance, you can create your own instance of context associated to your database and perform user login checking with your own logic. The most important part is probably the BasicAuthHttpModule class which handles the actualprocess of dispatching and authenticating the client request (particularly to access controller methods with Authorize attribute). So, to answer your second question, there are no necessary methods to retain as long as they're notconsumed in the client.

Let me know if you have any other questions.

Hope this helps,

Posted: March 4, 2016 6:35 AM

Hi Thomas,

The "white pages" doesn't seem to occur per our test. Could you re-check again if the issue persist? And also check on more devices or simulators to see if it's specific to an environment.

Posted: March 4, 2016 6:29 AM

Hello Thomas,

The Android Material experience doesn't support Indexing feature anymore. However, I've went ahead to create a feature request backlog for this item. As you might have aware, the rest of other Material features should work perfectly and live to the expectation for the final release.

Hope this helps,

Posted: March 4, 2016 6:22 AM

Hi Thomas,

Just sync'ing the latest state of these issues from the live chat session.

  • Running on API 15 and 16 device appears to work fine without crash, despite issues on certain samples which we'reworking on.
  • With production configuration APK, the sample works fine on API 17 device and simulator.
We'll getting back to you shortly after addressing minor glitches on the Material samples.

Thanks!

All times are GMT -5. The time now is 3:51 PM.
Previous Next