I would like to know is there any tool is available to compare dmn xml files and show the diff of decision tables.
I want to implement diff viewer for dmn xml files to show the diff of decision table using javascript. It would be greatly helpful if you provide any reference for already available diff viewer applications or any javascript npm plugins or any implementation using any language.
Let's consider below example. If decision table name is changed then I want to show only diff of name instead entire table, because if we change name of the table then the id will change. So it is difficult to find the table once we change the table name.
here is Jozef, a quality engineer for the DMN editor on the screenshot. Unfortunately there is currently no plan for a feature you describe in your question. Feel free to create a jira in https://issues.redhat.com/projects/KOGITO/issues
Related
Case:
I have csv data extract to be loaded with a great COPY INTO and also have a csv file with table description.
I want to create table from this description file before loading data.
Q:Is it possible to create a table by using description file?
I looked at 'CREATE TABLE mytable FROM LOADER myloader();' example but it does not seem support additional attributes to define columns.
One solution I know is to create a Python function to parse file and generate ddl statement but was curios if it can be done easier way.
Idea for enhancement: COPY INTO would be expanded to support creating tables at the same time by adding description file as another parameter.
Unfortunately, this is not currently possible.
The problem from my experience with implementing this kind of convenience feature is that it would be difficult to define a syntax that:
is backward compatible so that it does not break existing code
convenient for a majority of users
simple enough to implement
I have a question about informatica metadata, and i will be glad for any advices.
We can rightclick on any workflow in Informatica power center and choose
"Dependencies". After it, we see the window, where we can choose, what dependent objects we want to see.
When we press "OK", appears "VIEW Dependencies" window with list of dependent objects and info about them (object_name, object_type, timestamp, status, etc).
Does anybody know, how to select this list from informatica metadata repository tables? Or may be somebody know the way, how can i extract this select from power center designer.
I know about separeted views with mappings, sources, targets, etc, but may be you know, how to get exactly the same data, as on this window.
Thank you for any help
You need to realize that these data are in many different tables in the repository database, and it will be even more complex if you have versioning turned on in the repository.
We created a query that gives all dependent tables (sources, targets and lookup sources) for a workflow, but that took two of our smartest people more than a week, and still it has several drawbacks in a more generalized setting. One example is that it doesn't support worklets since we don't use it...
Can you narrow down the requirement, then we may be able to point you in the right direction?
We can check the dependencies through querying the Informatica repository Metadata tables. But for that we need to know the oracle connection details in which the metadata tables are resided(Mostly Informatica admins knows about the connection). If we get the connection details we can check the below tables:
OPB_MAPPING,
OPB_SUBJECT,
OPB_WIDGET(for transformations),
OPB_TASK,
OPB_WFLOW_RUN etc
Below is the sample SQL query that shows the names of all the Folders in the repository and the mappings contained in them along with last saved date, mapping version number and versioning comments, if any.
SELECT
S.SUBJ_NAME FOLDER,
M.MAPPING_NAME MAPPING,
M.VERSION_NUMBER VERSION_NUMBER,
CASE WHEN M.IS_VALID = 1 THEN 'YES' ELSE 'NO' END IS_VALID,
M.LAST_SAVED SAVED_ON,
M.CHECKOUT_USER_ID,
M.COMMENTS
FROM OPB_MAPPING M, OPB_SUBJECT S
WHERE M.SUBJECT_ID = S.SUBJ_ID
AND is_visible = 1
ORDER BY 1, 2, 3;
I'm working with Visual Studio Reports (rdlc files) for the first time, so I'm still quite new to it, and I don't know if this can actually be done.
I want to have a report that contains multiple tables of the same "type" (i.e.: with the same columns).
Now, obviously I can do this "by hand" by adding multiple tables to the designer. But here's the catch: I don't know beforehand how many tables I have to display!
So basically what I'd want is some sort of "repeater", a way to put "a list of tables" on the report, and then pass an array of data sources in code that would be used to populate them.
Can this be done at all? I don't see anything obvious in the designer that would allow me to achieve this... is it possible?
If not, could this maybe be done with a more advanced solution, like Crystal Reports?
If your tables have the same columns - use single table with the grouping by whatever criteria that defines "how many" tables you need to have. It would appear as if you have multiple tables on the resulting report. You can display report header for each group and if needed start each on new page.
Bottom line, don't think about it as multiple tables, it's the same table with the data driving how it is being displayed on the report.
Maybe helpful:
https://msdn.microsoft.com/en-us/library/ms251700(v=vs.90).aspx
http://www.codeproject.com/Tips/767067/RDLC-Report-Grouping-with-Page-Break-Table-Header
I'm currently developing my first MVC component for Joomla 3.x. All in all I'm bit struggling with language/translation issues in database.
My problem is that I need to store translated content of user generated content which comes from the backend. For example someone enters a new item in German (stored in database) and needs a translation in another language. How to accomplish that in Joomla? I don't like to generate a new item for every different language when the rest is all the same.
I thought about a table "item" and a table "item_language" with that structure (strongly simplified for viewing purposes):
item
id PRIMARY INT
price DOUBLE(4,2)
item_language
itemid PRIMARY INT
language PRIMARY CHAR(5)
name VARCHAR(50)
In item_language I would like to store the different translated versions. In the language field there would be the region code (eg. de-DE) to identify the language.
My problems:
How to display the different (translated) versions in backend?
Is this the right database model?
Any help is appreciated!
You have really found yourself a nice task for a first component in Joomla!
A rather generalist answer:
The database model seems right. Alternatively you could encode in JSON the language data, but this could make later query operations potentially difficult. This way you will only have one table to work with.
As far as I know (if you are using JModel / JTable to manipulate the data) can't do this directly, as JTable is really only designed to manipulate single tables.
What you can do:
For editing: figure a way to represent this graphically ( for your users to see and edit this one to many relationship) and to post this data (language texts as an array) to JModel. In the model you can maintain the desired relationships and save the data using JTable.
Viewing (without editing) shouldn't be an issue, it would be a simple JOIN.
If you are willing to create a basic component on github, I might even give you a hand with JModel / JTable.
I found a way to deal with the things I needed.
Thanks Valentin Despa for guiding me in the right direction :-).
Here the whole procedure (simplified - validations and exact steps omitted):
Define the form fields in the models/forms/site.xml as normal.
In views/site/tmpl/edit.php add self coded Javascript (based on jQuery) to deal with the fields which have content in multiple languages stored as JSON in database.
Clone the original form element and modify the needed attributes (id, name, ...) to display a special version just for the defined languages. As content - extract the JSON for the needed language from original field content and display.
Hide the original field with Javascript and append the customized versions to DOM.
Afterwards in tables/site.php I read the dynamically generated content withJInput and build together the original field by generating JSON and saving to database.
It's working like expected.
We currently have a Web Forms set up for our website and are looking to slowly convert this to MVC. Currently we store translations in a database. our translation table contains columns for each language and a sort of title. which we can identify the translation with(The primary key)
But it gets more complex when we actually may have different clients wanting different words for the same bit of text.
E.g. one will want it to read - Delivery Costs
And the next may want it as - Delivery Prices
So we then have a second CustomTranslation datatable which will be the same as the translation but also have a client ID number in it. If the user logged in and it looking for the Identify of the translation as "DeliveryCost" it will check to see if there is a record in the CustomTranslation table it will use that OVER the standard Translation table.
After which it will then pick the appropriate language the users wants.
Basically I need to be able to have our website translate depending on the users settings. And as well as the company they work for (our client)
The general method of localization uses resource files but we need to really keep them in the database. This produces a second problem which is when you try to declare Propertry Display Names and Validation Messages these also need to ability to have different text and/or translations but generally it expects a Static field which we would not have.
Whats the best way to go about solving this complex localization issue?
Thanks in advance. Steve
Problem 1 - Having the resources in the database
Use the approach used in this article for extending the standard resources into the database.
Problem 2 - Having custom localization per customer
No problem, the standard .net approach supports localization including a region or customer, just use i.e. en-US, en-US-Customer1, en-US-Customer2, etc.