I'm trying to add a Gantt-Chart (Oracle JET) with hierarchical data to my Oracle Apex (19.1) Application just like the example in the Cookbook (Hierarchical Tasks) by using the built-in implementation in Apex.
In this example, a JSON-file containing the tasks, which can have children-elements called subTasks gets parsed and rendered. However, I'm getting my data from a local database.
Is this feature possible in the Apex-version of oracleJET? Or do I have to implement the Gantt-chart from OracleJET as if it was a 3rd-party-solution?
Because I am able to create a normal Gantt-chart without a hierarchy, however, I haven't quite figured out, how to implement one with a hierarchy.
According to the documentation of ArrayTreeDataProvider, the default-keyword for child-elements to be located in is 'children'. But it doesn't matter how I format my data (selecting it from the database with json_object() and json_arrayagg() ), it only renders the 'parent' elements.
Does anyone have already implemented this/a similar functionality into an Apex Application and can help me out?
Thanks a lot in advance!
When I have had trouble defining a JET chart within APEX, I have always found it helpful to install the Sample Charts app from the App Gallery. Oracle does provide some sample Gantt charts with and without a hierarchy on Page 3 (in my instance of APEX 19.2) of the sample application.
Without knowing how your data is structured, we cannot provide an exact solution to your issue, but if you review the setups in the sample application, it should help you out.
I am trying out the sitecore speak ui applications. I am able to develop simple applications using speak.
I don't find any reference to how can we build SPEAK Pagecode file using C#.
I want to retrieve the data and save simple form using C# pagecode file.
Can any one guide me with an example?
I looked into https://doc.sitecore.net/speak/development/use_pagecode . But its of no help. I would like to know how can we bind the c# file to the SPEAK application and how to invoke functions.
To use the page code you need to edit the presentation of your page item. In Sitecore Rocks, go to the presentation details of your page item and double-click on the PageCode component to open the properties. There are 2 fields, PageCodeScriptFileName - that is for a JavaScript based page code, and PageCodeTypeName, in there add your fully qualified name of your C# class.
Credits to this post by Martina enter link description here
I am working on the upgrade of a project from Sitecore 6.2 to Sitecore 7.
I have found out that in Sitecore 6.2, the highlighting of the search results are implemented with the Lucene.Net.Search.Highlight.Highlighter, QueryScorer and Formatter classes in sitecore.client dll.
Which classes and/or functions does Sitecore 7 provide to do highlighting in search results? I searched the web but I could not find the required information/examples.
Highlighting of results is not supported currently OOTB with Sitecore 7 (it will be coming in a later version). The issue is that we map the results back to objects using the DocumentMapper so you do not have raw access to the 'Document' objects like the older versions.
For now, if you want to dig into Lucene and get the results yourself you can find the Highlighting functionality inside the Lucene.net contrib library.
If you do use this there is a useful blog post here regarding Lucene DLL versions that you should be aware of:
http://laubplusco.net/sitecore-7-lucen-3-0-highlighted-results/
I'm not sure if is possible to hightlight in search results.
On this link you can see: This little beauty is a hidden gem within the LINQ layer and in future versions of Sitecore will be your gateway to getting Highlighted Terms, Spelling Suggestions etc.
I just started to look into Sitecore and I was wondering if anyone can help me enlighten what / how it is exactly from a developer perspective.
I've gone through bunch of their documentation and also their SDN - seems to me so far most of them are just drag/drop click here and there through their interface (ie. through their "Sitecore Desktop") with very minor actual programming.
Is this true? or are their actual C# / ASP.Net programming behind the scene to implement business logic and such?
I went through their basic tutorial (creating basic site for Product), and like I mentioned above, it's all mostly done through their interface without any real programming - as opposed to working with the ASP.Net MVC3 Music Store tutorial where you can see some C# programming.
Thanks!
A Sitecore developer should have the most intense and deepest understanding of Sitecore in general. Developers need to understand the CMS user's perspective (i.e. content editor's POV), they need to understand the architecture of content within the content tree, and they need to know the code, which they build. A developer should have the most intimate knowledge of a Sitecore solution because you need to know the architecture to know how to code. And to know the architecture means you know how content editors will interact with the content.
Architecture
Sitecore is a souped up database. Think of it like that. You can architecture a site how you want. But once you start to learn the principles of Sitecore architecture and best practices you'll notice a pattern. Everything in the content tree is an item. The model for each item (called a template in Sitecore terms) is defined by an architect (which is often often a developer). In fact, even if there's a separate person for the architect role, they likely have developer knowledge as architecture defines the way things are developed. In fact, the architecture is one of the most important things.
Code
Code is broken down into various types, but in its simplest form there are two main things: layouts and sublayouts.
Think of a layout as what a normal a ASP.NET application uses a MasterPage for. In Sitecore, a layout is actually a ASPX WebForm, but it acts as a master page. Some examples of layouts you could have on your site are: One Column Layout, Two Column Layout, Print Layout. These would respectively translate to a header and footer with one main content area, a header and footer with a main column and side bar, and a print-optimized layout with maybe a logo and just main content.
Sublayouts are all of the little components that make up a page. Examples include: main navigation, a promo box in your side bar, a list of 5 recent news pieces, a CTA for a promotion, a sidebar slide show, etc. These components could be modular and moved around by content editors, or they can be fixed within the location of layouts, e.g. a promo box could always appear in the sidebar of the Two Column layout as a business rule defined in the code.
To answer your question about is there actual coding, yes. You write code using ASP.NET controls for Sitecore and Sitecore's C# API to access data that is populated into the templates on each item. So, if you had an item for a page that had a page title for the title tag, your code would use the Sitecore API to access the field "Title Tag" from the template (remember a template in Sitecore speak is a data model) in Sitecore.
Coding For Sitecore
I'd say there are two approaches to coding. I believe you identified one of them, which is using the internal tools within Sitecore's interface. Sitecore has a section called Developer Center that lets you create layouts and sublayouts. Frankly, compare this to using Visual Studio in Design Mode all of the time. I have never once used the Developer Center to do my coding. Instead, I code in Visual Studio which is the most common technique for people to code for Sitecore (at least I think it is). Now if you're wondering, how does the coding connect to Sitecore's data... well the answer is within Sitecore. There's a section of the tree called Layouts. In here are the names of your layouts and sublayouts. Each layout and sublayout item has a path that maps to either a ASPX WebForm or ASCX User Control, respectively. This is how the code on the file system that you write in Visual Studio actually gets used by Sitecore. These layout and sublayout items are then used via the Presentation > Details tabs for each item in Sitecore.
Beginners
One of the hardest things with Sitecore is the learning curve. I've been using Sitecore for years now and love it. In fact, its all I really do. It's by far my favorite CMS as its completely customizable and very developer-friendly. Sitecore recommends that new developers take the developer training classes so they can basically explain what I explained above in an actual training curriculum. In this training you will learn the architecture, and then how the code connects to it. Training involves hand-on architecture work within the content tree and hands-on coding. The recommend training courses for new developers are:
Getting Started With Sitecore Development: Sitecore XP 8 Website Development for .NET Developers (4 days, certification)
Further Training for Sitecore Certified Developers - Sitecore XP 8 Livefire MVC Workshop (1 day, no certification)
Sitecore is an ASP.NET application. That means that you can write any code you like. Our team creates all of the Sublayouts (ASCX files) and Layouts (ASPX files) ourselves in Visual Studio, not the editors built in to Sitecore.
Some installations of Sitecore that I have seen barely rely on the CMS to do the rendering. Instead values are pulled via the codebehind as if Sitecore was just a database. That can work fine in some situations.
The most impressive Sitecore instances use all of the available tools that the developer has access to. Using the Sitecore tools the way they were designed to be used allows some pretty impressive editing options for the (often non-technical) content editors.
For example: Using a Sitecore Fieldrenderer instead of just a placeholder or label will not only automatically render content appropriately (whether they are images or rich text), but it will allow the content editor to edit the content right on the web page as opposed to the only on back end that all CMS systems have.
Workflow is another killer feature for a customer that is the right size to afford Sitecore. It lets you build an approval process for items in the tree. That way legal, marketing and the graphics team call all sign off on a new page before it goes live. Then when all of the approvals are finalized, the site publishes automatically.
To sum up: Sitecore is a .NET application, you can code whatever you want. That means you should focus on the CMS features and make sure it is a good fit for you from a content editor perspective and a financial perspective.
Sitecore is in most cases just drag & drop as you've described in terms of content authoring but to actually turn this content into a webpage you need to implement layouts, sublayouts and so on.
Layouts are generic ASP.NET pages (aspx), sublayouts are just web controls (ascx) and if you prefer you can also use XSLT to generate HTML but it's useful only for basics (Sitecore only supports XSLT 1 at this moment). These ASP.NET controls are more less the same as standard web forms controls with code behind and so on. The difference is that Sitecore is your datasource and it gives you an APIs to access all relevant applications.
But Sitecore APIs also goes beyond that and allows you programatic access to virtually any component of the framework. The APIs are well docummented and quite easy to understand and they can be used for more complex scenarios.
Latest version of Sitecore (6.4) allows you to also use MVC framework for layouts/sublayouts creation if you don't like web forms that much.
Layouts and sublayouts are a great way todo any customizations from a coding standpoint but there is a third way that is not mentioned here. We call it sitecore extensions. I often find that to meet customer requirements, creating custom assembly's for workflow actions or template commands is the only way.
For example, a standard email notification upon entry into a workflow state only allows for you to apply server, recipient, description etc.. to action item field. In our case these values constantly change so we need to be more dynamic. A custom assembly applied to the action allows us the flexibility to do a number of things that the standard action will not. Another example was that we needed to have a treelist in an item scroll to and highlight the current item. The way todo this was to override the core treelist action with our custom assembly.
Keep in mind that adding alot of code to the layout (which could be a master page for a ton of pages) ramps up the runtime overhead.
From a UX perspective, Sitecore is impractical, overpowered and too complex to be effectively implemented for teams with typical content contributors and editors. No thought has been put into streamlining content creation or simple page template maintenance. I would never recommend Sitecore to a team without:
HTML authoring/editing skills
FTP concepts & Site tree understanding
Data management skills
The system is built for developers, with users as a very distant after-thought. In my experience, it offers a huge number of benefits — being a usable system for every-day content authors is not one of those benefits. The system is so modular and over-managed, it forces users on every level to make decisions that only complicate otherwise simple operations. Content publishing is extremely modular, and a big benefit for developers; it is a catastrophe for everyday users.
If you're a developer, Sitecore is a wonderful building environment. It's powerful and flexible.
If you're a user, Sitecore is task-heavy and offers the steepest learning curve I've ever encountered with a CMS. UAT has been a nightmare.
I'm not familiar with Filnet P8.
My assumptions from reading some online docs is that it has a central web-based user interface called Workplace which is implemented on the Java web stack and communicates with the core parts of Filenet through Java APIs.
Also it seems you can extend the Workplace trough JSR 186 compliant portlets. - from what I've read Filnet P8 Workplace is not a portal itself and cannot host portlets, but provides some of the functionality as portlets which can be used with 3rd party portals.
Filenet also seems to have a lot of extensibility points which don't require coding, but I'm considering a highly-customized application with custom dynamic grids and forms.
Is it possible to extend the Workplace using portlets and/or plain JSP/Servlet approach with custom GUI for a custom workflow? (Probably the "Web Application Toolkit" is the tool)
The GUI can contain grids with filtering and column selection, forms (not paper once) with dynamically disabling/enabling fields, custom search forms, dynamic context and dropdown menus.
The GUI should be able to integrate with the Content and Process engines of course.
A link to an existing Filenet P8 based solution which proves such a custom Workplace GUI extension possible would be great.
Thanks!
This is possible. First of all Workplace comes with FULL source code. Look in the AESource directory (usually in c:\Program Files\FileNet\AE if you are running it on Windows). What you need to decide first of all is where you want to plug in (for example do you want to create a new Wokrplace page altogether like the Browse and Search pages or do you want to splice it in as a new action like Checkout, Get-Info etc).
Once you figure that out, I can provide more specific information of where you want to look to add your new code. Once you can display an entry point to your own feature in Workplace, then you can use whatever you want as far as controls etc. You can use JSF grids or just classic JSP stuff or even JQuery controls (provided you link the right libs etc).
Another thing to keep in mind is that you are going to need to get familiar with the Web Application Toolkit (WAT) so that you can make sure you are getting the right state information from Workplace (like the user token of who is logged in, maybe what doc id the user clicked on, what folder they were in when they entered your UI).
Anyways, here is some info to get you started. If you provide more info about where you want to splice your UI in, I can provide some guidance as what you need to change etc.