As we write custom WebAPI applications, we need to take extra steps to secure sensitive information after deployment. Below is one of the steps you can take to encrypt the web.config file, which is a popular place where configurable sensitive information is stored.
Powerpoint slide
Cheers!
My Ellucian's Colleague playground with all tips and tricks I learned as a programmer.
Showing posts with label customization. Show all posts
Showing posts with label customization. Show all posts
Thursday, July 26, 2018
Saturday, March 5, 2016
self service "Could not validate this request's antiforgery token"
You may encounter this error while customizing Ellucian's self service. To fix this error, make sure you run the application in Local IIS, instead of IIS Express
After setting the default to Local IIS, you will want to delete all the cookies pertaining to the localhost. In chrome, go to Settings - Content Settings - All cookies and site data... then search for cookies belong to localhost
Delete these and try again. Similar steps should be taken with the browser you use to test self service.
After setting the default to Local IIS, you will want to delete all the cookies pertaining to the localhost. In chrome, go to Settings - Content Settings - All cookies and site data... then search for cookies belong to localhost
Delete these and try again. Similar steps should be taken with the browser you use to test self service.
Wednesday, July 8, 2015
How to get/query the list of files in a folder from Envision
Say you have a list of file in HOLD_SHARED_MYFOLDER directory in Colleague, and you want to read in the list of files in MYFOLDER and do something with them, maybe read or write or both.
What you need is read/write access to MYFOLDER. Your admin should know how to set it up, and a VOC entry should already be created for it.
In Colleague Studio, use the following code to get back a list of files inside MYFOLDER directory:
X.STMT = 'SELECT HOLD_SHARED_MYFOLDER'
CALL S.EXECUTE(X.STMT)
XL.FILES.NAME = ''
CALL S.READLIST(XL.FILES.NAME,0,X.STATUS)
CONVERT @FM:@SM:@VM:@AM TO @VM:@VM:@VM:@VM IN XL.FILES.NAME
Now you will have all the files' names in MYFOLDER populated in XL.FILES.NAME. To open each file up, you iterate them with S.OPEN.SEQ subroutine
FOR X = 1 to DCOUNT(XL.FILES.NAME, @VM)
* Open the file
CALL S.OPEN.SEQ("HOLD_SHARED_MYFOLDER", XL.FILES.NAME<1,X>, X, "R", X.ERROR.MSG)
* Read from the file
CALL S.READ.SEQ(X.TEXT, X.EOF, X, X.ERROR, X.MSG)
* Close the file
CALL S.CLOSE.SEQ(X, X.ERROR, X.MSG)
NEXT X
Tuesday, January 6, 2015
Colleague Lookup Resolution
EDIT: I have found that the "+Add" button can only be enabled if the lookup resolution is created in Colleague Studio. To get this to work, I created two lookup resolutions in two places, both with the same name and content (fields). One is created in Colleague studio, one is created in UICD. The names of these two need to be the same. Plug this on the form and it works (for me at least).
I found out today that creating LookUp Resolution in Colleague Studio sometimes doesn't work. When a lookup resolution is defined on the Resolution table field on LookUp Specifications Parameters screen of the file ID field, the default resolution table, which contains only Key and Description fields, is used instead.
To create and use a newly customized lookup resolution table, we have to do it in UICD, and then add the table name in Colleague Studio. First, go to UICD and create a new Context:
After adding the new context, detail into Search Results to define the lookup resolution:
Save out and go to Colleague Studio, enter the name of the resolution table into the Resolution table field.
Do not use the add button, since the new table won't be populated in there. Just enter the name of the table you created.
Save, regenerate the screen and you're done. Log out and log back in to see the new resolution table.
I found out today that creating LookUp Resolution in Colleague Studio sometimes doesn't work. When a lookup resolution is defined on the Resolution table field on LookUp Specifications Parameters screen of the file ID field, the default resolution table, which contains only Key and Description fields, is used instead.
To create and use a newly customized lookup resolution table, we have to do it in UICD, and then add the table name in Colleague Studio. First, go to UICD and create a new Context:
After adding the new context, detail into Search Results to define the lookup resolution:
Save out and go to Colleague Studio, enter the name of the resolution table into the Resolution table field.
Do not use the add button, since the new table won't be populated in there. Just enter the name of the table you created.
Save, regenerate the screen and you're done. Log out and log back in to see the new resolution table.
Subscribe to:
Posts (Atom)



