I am exploring boomi for now, I have a bit of working experience in Mulesoft. In Mulesoft, you can view the flow that you create in XML format in Anypoint Platform, and it can be viewed in the disk as well. Is there any such file created for Boomi processes? If yes, where are they located and how can I view them?
I can see that in the revision history of any component on the Build canvas in AtomSphere, you can view the XML of the component. Can I view the backend code for the whole process somehow?
Related
I'm on extended medical leave from my job and practicing at setting up my own workspace at home without the assistance of workspace setup documentation. I know I need a web.xml file somewhere in this structure but I'm not sure where it goes in the Web Content.
I'm only looking to create an input text field to enter a number and the user receives a number back from the tomcat server, but I don't know the proper place to create the Servlet java file in this particular folder structure.
My project has the standard Java Resources, Javascript Resources, build, and WebContent directories so far.
I've tried to Google for a similar project setup but no Youtube or Google workspace tutorial has shown the same workspace setup that I have. Does anyone know of one?
Yours Truly
(As Humanly Possible)
cnight62
I am writing a reporting app that runs in electron. Reporting means I have a data source and users write views that arrange the data in whichever ways they like so it can be printed out or archived as PDF.
Let's say there is a list of student data along with grades for courses. The reporing app allows you to create a report that has a data table with names and grades for each course. So you end up with grade reports. Someone else wants just names and addresses another one wants to create a library card for each student. HTML and CSS combined with Vue make a great foundation to write this stuff.
The easy part is to fetch data from the database and offer json as a data source to views. The difficult part is how to let users add their reports to the app. In dev mode I can just add views to directories, import them and render the data as part of the app. But I have my views available at build time. Once I have built and shipped the production app it's out of my hands and the user can't add their views to the app anymore because they don't rebuild the app. They just want to point to a directory, add their views and use them.
I have decided to use single file components because they allow users to simply add calculations and maybe use pug etc to keep it simple. Besides I can store data about the component in a straight forward way (like name of report, department etc)
To my knowledge I need to build those views programmatically and load them dynamically.
So my questions are:
How can I build and mount single file components (.vue) dynamically
from within a production app that has no prior knowledge of user
produced files?
Do I need to build these components or is there a way to utilize on board tools to just read and render these components?
Is there a better way to serve these files?
More information:
Security is not a concern. So loading user created views is ok. It needs to be working in electron. I do have a server based app written in Ruby that does the same thing but the server is going away anytime soon so it has to be client based and executable. I cannot install node on client PCs so they could just build their own app and include their own views via hot reloading.
If you're interested in reporting apps there is one in JS but server based: https://jsreport.net/ or mine, ruby based: https://github.com/hmt/sahib
You could watch the directory and respond to new files being add. That's for the dynamic part of your question. A nice way is node-fs.
Using the same lib you can serialize and deserialize object to or from file, letting you load the file from your user.
At this point, you only need to be able to change back and forth from an object to a Vue component. As far As I know, this is no problem as you can
new Vue (object)
According to requirement of application, I have developed a custom web part in Kentico 9. This web part is using with same functionality at various places but we have to use with different layout structure.
As per my understanding, we can create custom layouts for a single web part from "Layout Tab" in web part configuration. As I used same things with various Kentio built in web part like Logon form, Logon-Mini form, etc.
But while trying to create new layout for my custom web part, I am getting web part loading error and when I checked into event log it is showing following error:
The file
'/CMSVirtualFiles/WebPartLayouts/=vg=87a868ce-926c-4cb3-a441-b4f1d4310afc/TDNForgottenPassword/ForgottenPassword.ascx.cs'
does not exist.
Here, internally system looking for ".CS" file under "CMSVirtualFiles" folder, which has actually under the "CMSWebParts" directory in which I have created my user control.
Is there any specific configuration required in custom web part to implement multiple layout of it? Please help me and guide me, what am I missing or doing wrong?
Check your webpart code file property in the ascx file. You need to specifically declare the full relative path to the .cs file and not just the filename. For example:
Correct
CodeFile="~/CMSWebParts/Community/GroupRegistration.ascx.cs"
Incorrect
CodeFile="GroupRegistration.ascx.cs"
Please make sure you don't have the store virtual files in the file system setting enabled.
The snapshot of service data is good to use in development as I first write the service and see if it's returning data and then write the view. However after I upgraded to ServiceStack v3.9.45 it looks like the Razor2 plugin prevents snapshot information being generated. Probably the request never gets that far if there is no view for it.
Is it possible to have the best of both worlds and return snapshot data if there is no defined view? :)
Background
My task is to, in SharePoint, show an image of a process map which should be clickable. Think of an imagemap in html. Some areas take you to other process map images and other brings up a pop-up window.
"Connected" to each process map is a set of documents. These documents are stored in a document library. There are one process map for each folder in the document library. The documents should be shown next to the image. The person clicking either the image or a folder to navigate in the hierarchy should also be able to upload, download and delete the documents.
Question
What would be the easiest solution for this?
My thoughts
... so far is to create a custom web part which I add above the document library browser (the default one in MOSS 2007). This web part reads some xml file pointing out the image to show and the areas which is to be clickable. It listens for some kind of events from the document library, like clicks on folders in the browser or it reads the current URL to know where in the folder hierarchy we are currently, and from that show the correct process map image. When the image is clicked, the web part updates the image and tells the document library to update accordingly.
Is this feasible? Am I on the wrong track? How do I communicate with a document library?
Thanks, Martin
My thoughts are that you create a web part that displays your image map and outputs(provider) the appropriate criteria to a another web part that consumes it and displays the files in a document library.
You can achieve this by creating your own custom webpart that displays a document library based on a CAML query. Each Images sends a different CAML query to the document library webpart.
I hope this helps. Please provide information on how you solved this problem if you have already done so.
Thanks
Long since I've been here... Actually solved this one.
We created two web parts, one for process navigation and one for filtering documents in the document library.
The web part for process navigation is actually just a web part that looks for a specific query parameter in the URL and adds ".html" to it. Then looks for that document in a document library. If found then this document is shown inside an iframe. Simple!
The html documents are produced by Visio and exported to html, then uploaded to SharePoint. The links in the Visio document drives the application with queries.
The web part that shows the corresponding documents also looks for a specific query in the URL then sends filterparameters to the document library through the IfilterProvider interface. I snatched this example IFilterProvider at MSDN and made it look in the URL for parameters and then made the controls invisible to the user.
Really simple solution, though the customer needs to put in a lot of work to incorporate their company processes into it. And it is somewhat error prone and probably a sucker to make changes to data-wise.