Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How do you add a security group to a live app without losing other security information?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How do you add a security group to a live app without losing other security information?

    I have an app that has been in use for years.

    The app provides the ability to add users and assign them to existing groups.

    I now need to add a new security group which I can do in my dev environment, but if I publish the security files to the live environment, security information in the live environment is overwritten. For example users that were added are lost.

    How do you add a security group to a live app without losing other user information?

    #2
    Re: How do you add a security group to a live app without losing other security information?

    There's no information here about the security setup you're using or the Alpha version you're using. There are multiple security setups available.

    If it's SQL table based then you can add records to your security tables manually. Further, if you need to add existing users to a new security group, then you could do that with XBasic.

    Comment


      #3
      Re: How do you add a security group to a live app without losing other security information?

      V12.4.5.4.7 Build 5487

      Using Alpha's tables. Just need to add a new group without overwriting current user info but can't see a way to do this.
      Last edited by [email protected]; 12-13-2018, 11:05 PM.

      Comment


        #4
        Re: How do you add a security group to a live app without losing other security information?

        Using Alpha's.... SQL... tables ? If so, then... using a tool like Navicat... access your tables and add a row to websecuritygroups.

        Comment


          #5
          Re: How do you add a security group to a live app without losing other security information?

          I was using the standard alpha files/tables to store user/group security info. I was also storing some additional user info in an sql table in my db.

          There is a built in function a5ws_Add_Group("myNewGroup") which you can call from a button for eg and it does create the new group in your live env. This would be the same as adding the group using a tool like Navicat.
          You can then add users in your live env to the new group using components you have built such as the templates alpha provides.
          You can then create the same new group in your dev env, assign new group permissions to components/pages etc
          But there is a catch, you have to publish the web security data files/tables in your dev env and upload these to your live env or else alpha's security will deny access to users in the new group. This is an issue if your live env allows users to be added/edited because your dev env and your live env will usually have different users.

          So this is how I overcame it.

          I copied all of the files that start with websecurity_ from the live env to my dev env.
          I also copied my sql database from the live env to my dev env because I store additional user info in it.
          I then created the new security group using the dev env user/group dialog.
          I then assigned the new group to the various components etc
          I then published my app locally and ran it, then added the users to the new group using my "manage security" component.
          I then copied/published all of the files that start with websecurity_ back to the live env, and also the sql db and any components using the new group.

          Worked a charm and I hope this helps others that might be faced with the same situation.
          Last edited by [email protected]; 12-15-2018, 11:28 PM.

          Comment

          Working...
          X