Edge Enable Npapi
Garland Flugum
We have a sites.xml that redirects people to Edge for IE Mode sites. That is working perfectly, no issue with that and it works for many people. However, we do have a handful of people that when it attempts to use Edge in IE mode it says:
On the address bar in Chrome, type chrome://flags/#enable-npapi.In the Enable NPAPI Mac, Windows box, click Enable.Exit and then restart Chrome.Reopen the Silverlight page.Right-click the broken puzzle piece image, and then select Run this Plugin.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
You should apply a patch policy to regularly update the machines, it is the responsible thing to do. Internet Explorer and certain system components require certain patches to be applied for seemless integration with Edge IEMode.
FYXPCUSR Procard User Extract Report Update
The FIS Banner Procard User Extract (FYXPCUSR) report has been updated to include card-type CTE and Level 2 Org Code reporting and retitled Procard/CTE User Extract Report. Click here for more information.
The FIS Banner Procard User Extract (FYXPCUSR) report has been updated. The report, retitled Procard/CTE User Extract Report, includes updated parameters for card-type, and Level 2 Org Code. The updated card-type paramter means that departments can now receive reports on their active CTE cardholders as well as their VISA cardholders. The addition of the new Level 2 Org Code parameter means that departments can see cardholders within their Level 2 Org structure (e.g. Org Lvl 2 19 will return a list of ALL active Procard cardholders with card accounts that roll up to 19).
Banner Messaging/Disapproval Notifications are new with this upgrade. This feature notifies users when their documents (invoices, journal vouchers, purchase orders and change orders) have been disapproved. GUAMESG is intended for Banner users who input documents into Banner that require approval from another Banner user. Click here for more information.
These dates are tentative, and subject to change. We have decreased class sizes to allow for greater distance between people. If you have enrolled in any of the March or April training dates, we have re-enrolled you into a May training date and you will be receiving an email with additional information. If these rescheduled dates do not work, please let us know via email to fistr...@ucsc.edu.
Safari version 12 is incompatible with FIS Banner
Beginning with Safari version 12, NPAPI plugins including Java are no longer supported. Unfortunately, the Java plug-in that FIS Banner requires is an NPAPI plug-in.
ITS Client Services & Support has identified an alternative browser, for Mac users, called Waterfox that supports NPAPI plugins. Look for the BigFix offer "Install Waterfox - A Java Compatible browser", which has been sent to affected users. If Safari has already been updated to version 12, you will need to accept the BigFix offer for the alternative browser, Waterfox.
ITS Client Services & Support has identified an alternative browser, for Mac users, called Waterfox that appears to support NPAPI plugins, and FIS Banner. Look for the BigFix offer "Install Waterfox - A Java Compatible browser", which has been sent to affected users. If Safari has already been updated to version 12, you will not be able to login to FIS Banner from that Mac using Safari.
FIS Unavailable Saturday, August 4th at 7am to 2pm
We will be performing the Budget Roll on August 4th to carryforward remaining budgetary balances from FY18 into FY19. FIS will be unavailable Saturday, August 4th, at 7am until mid-afternoon, same-day. Please contact us at fis_...@ucsc.eduif questions.
FIS Unavailable 12pm Monday August 8th to 7am Tuesday August 9th
We will be performing the Budget Roll on August 8th to carryforward remaining budgetary balances from FY16 into FY17. FIS will be unavailable Monday, August 8th, 12noon to Tuesday, August 9th, 7am. Inception to date reporting data will be available on Friday, August 12th. Please contact us at fis_...@ucsc.edu if questions.
ITS will be installing a patch to fix some issues we've encountered in FIS with the newest versions of Java. FIS will be unavailable at 7am tomorrow morning, Saturday, 7/25/2015, for approximately one hour while the patch is applied.
To ensure that your system is picking up the new patch info, please close all your open browser sessions and start FIS from a fresh browser launch the first time you login after this weekend.
And, of course, if you have any difficulties, let us know at fis_...@ucsc.edu. We'll be standing by.
FY15 GL and Encumbrance Roll Processing COMPLETE
The FY15 General Ledger and Encumbrance Rolls were successfully completed on Saturday, 7/11. All fund balances and open encumbrances were rolled forward into FY16. All documents must now have a transaction date in July 2015 for posting to ledgers. Period 12 is now closed.
We've added an FIS Quick Start Guide (handy for newbies), as well as an FIS Key Dates calendar that calls out period close and FIS training dates, and on which we will also add any FIS planned downtimes.
The webpage has also been migrated to the financial.ucsc.edu (Financial Affairs) web servers, so you'll see the standard Financial Affairs menu bar at the top, giving quick navigation to all the guides and other resources available there.
Enabling Java Plugins in Chrome
Beginning with Chrome 42, NPAPI plugins are in the process of being retired and must be enabled. If you are seeing an error stating "This plug-in is not supported" when starting FIS in Chrome, please click HERE and follow the instructions to enable the NPAPI Plugins.
FIS Password Resets Required
As of Saturday, February 7, 2015, FIS passwords will be case sensitive. All users will be prompted to reset their FIS passwords the first time they login after Saturday. FIS password rules are not changing, and mixed case passwords are not yet required; however, we do encourage you to use mixed case in your FIS password to enhance security. FIS password rules are available for review here. If you have trouble resetting your password, please contact us at: fis_...@ucsc.edu.
You can call .NET functions from Node.js and Node.js functions from .NET. Edge.js takes care of marshalling data between CLR and V8. Edge.js also reconciles threading models of single threaded V8 and multi-threaded CLR. Edge.js ensures correct lifetime of objects on V8 and CLR heaps. The CLR code can be pre-compiled or specified as C#, F#, Python, or PowerShell source: Edge.js can compile CLR scripts at runtime. Edge can be extended to support other CLR languages or DSLs.
If you want to use .NET Core as your runtime and are running in a dual runtime environment (i.e. Windows with .NET 4.5 installed as well or Linux with Mono installed), you will need to tell edge to use .NET Core by setting the EDGE_USE_CORECLR environment variable:
Edge provides several ways to integrate C# code into a Node.js application. Regardless of the way you choose, the entry point into the .NET code is normalized to a Func delegate. This allows Node.js code to call .NET asynchronously and avoid blocking the Node.js event loop.
The true parameter instead of a callback indicates that Node.js expects the C# implementation to complete synchronously. If the CLR function implementation does not complete synchronously, the call above will result in an exception.
One representation of CLR code that Edge.js accepts is C# source code. You can embed C# literal representing a .NET async lambda expression implementing the Func delegate directly inside Node.js code:
In another representation, you can embed multi-line C# source code by providing a function with a body containing a multi-line comment. Edge extracts the C# code from the function body using regular expressions:
If your C# code is more involved than a simple lambda, you can specify entire class definition. By convention, the class must be named Startup and it must have an Invoke method that matches the Func delegate signature. This method is useful if you need to factor your code into multiple methods:
If you integrate C# code into your Node.js application by specifying C# source using one of the methods above, edge will compile the code on the fly. If you prefer to pre-compile your C# sources to a CLR assembly, or if your C# component is already pre-compiled, you can reference a CLR assembly from your Node.js code. In the most generic form, you can specify the assembly file name, the type name, and the method name when creating a Node.js proxy to a .NET method:
If you don't specify methodName, Invoke is assumed. If you don't specify typeName, a type name is constructed by assuming the class called Startup in the namespace equal to the assembly file name (without the .dll). In the example above, if typeName was not specified, it would default to My.Edge.Samples.Startup.
The assemblyFile is relative to the working directory. If you want to locate your assembly in a fixed location relative to your Node.js application, it is useful to construct the assemblyFile using __dirname. If you are using .NET Core, assemblyFile can also be a project name or NuGet package name that is specified in your project.json or .deps.json dependency manifest.
4a15465005