A common place for all K2 tips, tricks and components. We currently have 6 categories defined in which assets are categorized. There is also some getting started documentation to cover areas of interest and how-to documentation.
Each app or component has its own repo in order for us to version them individually. Whenever a reference is made directly to a component hosted here, the best practice is to link directly to the version you are building against. This approach will prevent us from running into issues if later versions of the component introduce breaking changes.
Here's how the assets are broken down:
All the completed apps, immersified or standard, will be categorized as such.
Used for all those reusable views, forms and scripts that we can simply drag and drop onto the canvas, set a view values and have it do its thing.
Here we store any custom CSS we created. There are some generic ones in the root, but we can also create specific themes and group them together in sub-categories.
List of images we can reuse. They can be linked directly from GitHub or saved to your repository of choice. There will only be a single repo for all images, with folders to separate these by theme, icon set, etc.
Reusable scripts for common actions like animation, control behavior and so on. The idea here is to have a bunch in the root, with more specific scripts in sub folders. These files will also be versioned as a single unit. The key differentiator between having a script here vs common components is that if the script renders something new, it's probably a component. If it alters behavior of existing controls or actions, it belongs here.
JavaScript files cannot be linked directly from the GitHub repo, it has cross site scripting prevention headers, we need to proxy it through something in order to have them served correctly in SmartForms. There is a nice little site that does that for us, details are in the JavaScript Files form.
For all the custom components we create for the JSSP. Each will have its own repo and version. Each component will also need to be documented thoroughly to ensure ease of use.
NOTE: The apps have not been ported over yet. The links below do not work. Ping the team if you have an app request.
Order parts and acknowledge receiving them by phone.
This component allows one to lookup addresses using the Google Maps APIs. Because it uses autocomplete to best guess addresses as you type, it doesn't make sense to have this as a service instance. This implementation is using JavaScript on a reusable view, with only some simple setup needed from the developer's side to get this going.
Lite version of an Excel import using combination of JavaScript and SQL Server stored procedures to import data from a selected Excel spreadsheet into a SQL Server table.
With the Signature Pad, you can capture signatures as part of the approval steps of the request. One can scribble using your mouse or finger on touch-screen devices. You can also redraw the signature for read-only views of the request.
These are generally stand-alone. Some key files are:
- TBD1
- TBD2
Similar to CSS files, these tend to be stand-alone. Some key images are:
- TBD1
- TBD2
Similar to CSS files, these tend to be stand-alone. Some key files are:
- TBD1
- TBD2
All the custom components we create for the JSSP.
Azure Content Analytics - TODO: Update when move is done
An Azure Analytics broker supports the following interfaces:
- Text Analytics:
- ModerateText (based on content moderator v1.0 API)
- GetSentiment (based on text analytics v3.0 API)
- Image Analytics: (based on vision analytics v2.0 API)
- ListCelebrities
- ListTags
OpenWeather API - TODO: Update when move is done
Get Current Weather (City, Units) ---- Units: Imperial/Metric
ServiceNow - TODO: Update when move is done
Supports the following ServiceNow Incident interfaces:
- ListIncidents
- GetIncident
- Create Incident
- Update Incident