Announcement

Collapse
No announcement yet.

New bug introduced with the last update

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • New bug introduced with the last update

    At this moment my scriptcase is completely up to date with the latest update 7.01.0014 including that last update of 2 files.

    I had this statement for oracle in my SQL in the form:
    Code:
    SELECT
       s.STEPID as STEPID, 
       s.CASE_ID,
       c.MUTFORM_NR,
       c.forminfo,
       s.CASE_FLOWSTEP,
       s.STARTDATE,
       s.REMARKS,
       s.EMPLID_CTRL,
       s.STATUS,
       s.CASE_FLOWSTEP_SEQ,
       s.RESULT,
       s.RESULTDATE,
       s.RESULTREMARKS,
       s.EMPLID_ADMIN,
       s.EMPLID_CLAIM,
       s.SC_APPID,
       s.DEADLINE,
       s.ROLE_CTRL,
       s.EXT_CONN_STR,
       s.EXT_EMAIL,
       s.RUG_EMPLID_DELEGATE,
       'Afhandelen' as SHOWSCREEN,
       '' as WORKFLOW
    FROM 
        SCRIPTCASE.MUTF_CASESTEP s,
        SCRIPTCASE.MUTF_CASE c
    WHERE
      s.CASE_ID = c.CASE_ID AND 
      s.STATUS='OPEN' and
    
      s.EMPLID_ADMIN <> '0' and   
      s.EMPLID_ADMIN like ['glob_werklijst']
    
    UNION
    
    SELECT 
       s.STEPID as STEPID, 
       s.CASE_ID as CASE_ID,
       c.MUTFORM_NR,
       c.forminfo,
       s.CASE_FLOWSTEP,
       s.STARTDATE,
       s.REMARKS,
       s.EMPLID_CTRL,
       s.STATUS,
       s.CASE_FLOWSTEP_SEQ,
       s.RESULT,
       s.RESULTDATE,
       s.RESULTREMARKS,
       s.EMPLID_ADMIN,
       s.EMPLID_CLAIM,
       s.SC_APPID,
       s.DEADLINE,
       s.ROLE_CTRL,
       s.EXT_CONN_STR,
       s.EXT_EMAIL,
       s.RUG_EMPLID_DELEGATE,
       '' as SHOWSCREEN,
       'Workflow' as WORKFLOW
    FROM 
        SCRIPTCASE.MUTF_CASESTEP s,
        SCRIPTCASE.MUTF_CASE c
    WHERE
      s.CASE_ID = c.CASE_ID and
      s.STATUS='OPEN' and
    
      s.EMPLID_CTRL = '0'  and
      s.EMPLID_ADMIN = '0'  and
      s.ROLE_CTRL = 'AM' and   
      s.EMPLID_CLAIM like ['glob_werklijst']
    This worked before that last update of scriptcase of the 2 files. Now it doesnt anymore...
    Meaning if I use a union then scriptcase can not find the columns anymore. Then only way to resolve that is the following workaround:
    Code:
    SELECT
       s.STEPID as STEPID, 
       s.CASE_ID,
       c.MUTFORM_NR,
       c.forminfo,
       s.CASE_FLOWSTEP,
       s.STARTDATE,
       s.REMARKS,
       s.EMPLID_CTRL,
       s.STATUS,
       s.CASE_FLOWSTEP_SEQ,
       s.RESULT,
       s.RESULTDATE,
       s.RESULTREMARKS,
       s.EMPLID_ADMIN,
       s.EMPLID_CLAIM,
       s.SC_APPID,
       s.DEADLINE,
       s.ROLE_CTRL,
       s.EXT_CONN_STR,
       s.EXT_EMAIL,
       s.RUG_EMPLID_DELEGATE,
       CASE WHEN 
    		s.EMPLID_ADMIN <> '0' and   
    		s.EMPLID_ADMIN like '%'
       THEN
    		'Afhandelen' 
       ELSE
        '' 
       END as SHOWSCREEN,
       CASE WHEN
    		s.EMPLID_CTRL = '0'  and
    		s.EMPLID_ADMIN = '0'  and
    		s.ROLE_CTRL = 'AM' and   
    		s.EMPLID_CLAIM like '%'
       THEN
        'Workflow'
       ELSE
        '' 
       END as WORKFLOW
    FROM 
        SCRIPTCASE.MUTF_CASESTEP s,
        SCRIPTCASE.MUTF_CASE c
    WHERE
      s.CASE_ID = c.CASE_ID AND 
      s.STATUS='OPEN'
    Bug fixes are supposed to make things better not worse!! Please check your fixes better.
    I have said this before, put a test team to work and make test scenarios and test it before you release an update....

  • #2
    And then there is another bug introduced with it I just noticed.
    If the application is generated with the above sql (in a grid) then the grid gives errors that it cant find case_id and various other related variables. This was working properly before the last update.
    So now I have to change this:
    SELECT
    s.STEPID as STEPID,
    s.CASE_ID,
    c.MUTFORM_NR,
    c.forminfo, ....

    to this:
    SELECT
    s.STEPID as STEPID,
    s.CASE_ID as CASE_ID,
    c.MUTFORM_NR as MUTFORM_NR,
    c.forminfo as forminfo, ...

    to make it work properly..

    Please test your updates better!!

    Comment


    • #3
      Apart from that, if you use any FIELDNAME as something then the types are also lost.
      So basically this part is full of bugs...
      So in short:
      select field as f from table makes it so that the type isnt detected anymore.. BUG BUG BUG!!
      select a.field1 as f1,b.field6 as f2 from a,b seems to be buggy..

      Comment


      • #4
        Aparently if you remove links completely save it generate it and remake the links it suddenly works again...
        buggy.... well so now everyone knows

        Comment


        • #5
          Hello,

          Issue reported to our bugs team.

          regards,
          Bernhard

          Comment

          Working...
          X