Impact field in OTRS 5.0.13 - otrs

I am new to linux. I am looking into OTRS.
I installed OTRS 4 and have upgraded to 5.0.13 and the upgrade was seamless.
I have not managed to find the solution for this problem I have.
I see 2 Dynamic fields already created by system by the name ITSMImpact and ITSMCriticality.(These got installed after I installed packages) Here is my problem.
When I am trying to create a ticket on behalf of the user
I am seeing that the impact field is present but has no dropdowns
I am seeing that the criticality field is not present.
I am so confused due to the numerous fields in sysconfig. Not even sure how to search. Can someone be kind enough to tell me which module should I go to so I can find the fields listed during
Creating a new Phone ticket
Creating a new Email ticket
Thanks in advance.

Related

How to keep track of versions of a D365/Power Apps portal application form

Apologies if the title is not clear as I was not sure what to set it to. Also, I was not sure whether to post this question here or in a Power Apps forum as my problem also involves that platform.
I am in need of advice on the best way to create a system I'v been tasked to create.
The system in question is going to provide our customers with an online application form to apply for some of our services. This application form is to be created using a Power Apps portal form and the data is to be saved in D365 entities. The application form will be collecting a lot of information about applicants such as their personal and contact details, joint applicant (if any), employment history, current and old addresses, residency history, etc.
The application has a unique reference number. Once an application is submitted, it will be reviewed and will either be accepted or rejected by the admin team. But during its review or even after it's been rejected, the admin team could allow the applicant to make changes to the application on the applicant's request. For instance, if the application has been rejected because the admin team did not find the joint applicant suitable for the application, the applicant could ask the admin team to allow them to amend the application to remove that joint applicant or replace them with another applicant.
Here's the important part. Because an application can be amended during its life before it has been accepted or rejected for good, the admin team need the system to keep track of all changes made to the application. Therefore the system should support a version history of the application. This should include a version number so that every time a new version of the application is made, the version number is incremented. And all versions will be pointing to the same application, i.e. they will hold the unique reference number of the application.
Finally, the admin team wants the ability to send the applicant the link to the specific version of the application the applicant wants to amend or update (which is usually the latest version but it could be an older version) so that when the applicant clicks the link the Power Apps portal form will load all the details of that version for the applicant to access.
I most appreciate any advice the good experts here can provide for the above scenario.

WSO2 Identity Server - Force users to fill out security questions for password reset

I need to force my users to fill out the security questions for self service password reset. Ideally when they log into a SP it reads our active directory for the custom attribute associated with the security questions. IF that is blank then force the user into the wso2is dashboard/security questions area.
IS THIS POSSIBLE????!!!!????
Thank you for any assistance.
I have looked through all of the wso2is documentation and forums looking for a solution, still have yet to come across anything.
So I found the answer, it is now included in version 5.7.
https://docs.wso2.com/display/IS570/Managing+Challenge+Questions
Very bottom of article.
Upgrading is fine but if 5.7 can do it, 5.3 should also be able to. Oh well time to upgrade.

Sitecore Custom profile

Using Sitecore 7.1, we have defined a custom profile with a custom user profile .Net object so that the user's values can be updated in the Security Manager.
In our site, we have a page to display the current user's profile.
If I update a user's details in the Security User Manager, I expect them to be updated on this page. This works fine locally but when we deploy to test (which has separate authoring and delivery servers), the updated details aren't displayed on the page. We have a custom database table that does contain the correct values so I don't know where the incorrect values are coming from (should I be looking at aspnet_Profile table?) ..
We are using IAuthenticationManeger.GetActiveUser().Profile to get the user to display.
Any ideas? Let me know if supplying any other code would help ...
If your are overriding the Sitecore.Security.UserProfile class and using SetCustomProperty method, then yes the values are saved in the aspnet_Profile database. If you update a user profile in a dev environment, you would need to copy those changes to your test environment via serialization or package to see them there.
If you are doing something else, then you may want to post the code for your profile class so we can get a better idea of what is going on.

Liferay User Private Pages has no inheritance

within a project I encountered a problem with the Liferay inheritance/propagation. I added 3 pages to the "User private pages" Site template (as child pages of an already existing page, if that matters). I expected, that all users would have these pages available. But in fact, they have not. When opening one of the new pages, it says page not found. I can solve this by manually going to the private pages root page of that user, which seems to activate the propagation which leads to a generation of the new pages.
I wasn't able to find something related on the web. Is this a known bug? Am I just unable to find the correct settings?
Please help.
Regards
LifeRay BugTracker, STATUS: Under Development, AGE: 11 weeks, 1 day
I recommend using the GIT to set LifeRay Portal to commit ID f5ce41ae4424e47230e7222294559f94656acd22.
This feature is reported to work under that commit ID. I am performing a GIT bisection to replicate this issue on my system, and attempt to fix it by applying the patch I will find at the commit ID captioned above.

django-registration with custom user

I have searched high and low and found no complete answers. Nothing seems to work. I'm fairly new to django but it seems that what I'm doing should be fine. I don't want to have my members sign up with a username. I hate usernames. Just the email address and password is needed. So I'm forced to make a custom user (the way I understand it). After that adjustment nothing seems to work. I just want django-registration to accept my custom user but it can't. I have tried a handful of forks on github that claim to have updated the registration to accept custom users. They don't seem to work. My questions are:
What is a valid version of django-registration that allows for custom users?
How do you install that version?
Maybe I'm doing something wrong in installing it...
I am able to log into my administration and I'm able to log into the user account that was created when I created my super user account (command line). My only problem is that I am unable to sign up as a new user. I'm just taken to the sign up page again after submitting. If I don't fill in all the required sign up info I see the expected notices so the code is partially working. The database doesn't show a new user either. Hopefully someone can help me because I've been researching and trying new things for days.
Thanks
I would simply comment, but due to my lack of posting am unable. Anyways...
As lalo stated, django-registration doesn't really support custom users. You could try doing this. I added an extra field to my model and made those changes, which allow me to create users but failed to save the value of my extra field.
So I would say that custom users + django-registration can be done, but you will likely end up overriding many classes/methods provided in django-registration and thus it may be easier to try to create it all from scratch. That's my brief experience, at least.